Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Helper

Checked
davila7·vlatest·backend·MIT

Automates Git commit message generation based on code changes and project conventions, streamlining your workflow.

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 davila7/claude-code-templates --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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/git-commit-helper/SKILL.md
Scanned
1 file, 190 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

The Git Commit Helper skill assists users in generating well-formatted and meaningful commit messages for Git repositories. It analyzes changes made in the codebase and suggests concise, descriptive commit messages following conventional standards like Conventional Commits.

When to use it

  • Before pushing a set of local changes to a remote repository
  • When you want to ensure your commit message follows best practices or team conventions
  • After making multiple small changes and need a summary for each change
  • To save time when writing clear, standardized messages manually

Key capabilities

  • Suggests commit message formats based on code changes
  • Follows Conventional Commits standards (e.g., feat, fix, docs)
  • Analyzes diffs to infer the purpose of changes
  • Provides multiple message options for user selection

Example prompts

  • "Generate a commit message for these changes in the auth module."
  • "What is a good conventional commit message for this diff?"
  • "Suggest a concise and descriptive commit message based on my code changes."

Tips & gotchas

  • Ensure your working directory has staged changes before using the skill, as it analyzes diffs.
  • While it provides suggestions, always review the message to ensure accuracy and context relevance.