Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Helper

Checked
89jobrien·vlatest·backend

Automates Git commit creation with pre-defined templates and descriptions based on task context for streamlined backend workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it Git Commit Helper, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add 89jobrien/steve --skill "Git Commit Helper" -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

89jobrien

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned 89jobrien/steve at c0ff044bf0.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c0ff044bf0
Manifest
steve/skills/git-commit-helper/SKILL.md
Scanned
2 files, 322 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists with crafting effective and informative git commit messages. It can generate a suggested commit message based on provided changes, ensuring clarity and adherence to best practices. The tool aims to streamline the commit process and improve code maintainability by creating well-formatted commit histories.

When to use it

  • You've made several changes to your codebase but are unsure how to summarize them in a concise commit message.
  • You want to ensure your commit messages follow a consistent format within your team or project.
  • You’re working on a complex feature and need help articulating the purpose of your commits.
  • You're new to git and want guidance on writing good commit messages.

Key capabilities

  • Generates suggested commit messages based on changes.
  • Promotes clear and concise commit descriptions.
  • Supports adherence to established commit message conventions.

Example prompts

  • "Generate a commit message for these changes: [paste diff output]"
  • "Suggest a commit message summarizing the refactor of the authentication module."
  • “Create a commit message based on this file’s modifications: src/components/Button.js”

Tips & gotchas

The skill's effectiveness relies on providing accurate and comprehensive information about the changes made. While it can generate suggestions, always review and adjust the generated messages to ensure they accurately reflect the work performed.