Skip to content
TrustedSkillsbeta
Back to all skills

Commit Helper

Checked
peopleforrester·vlatest·backend·MIT

This "Commit Helper" suggests descriptive commit messages based on code changes, streamlining collaboration and improving Git history clarity.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add peopleforrester/claude-dotfiles --skill 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

peopleforrester

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 peopleforrester/claude-dotfiles at db7caa0374.

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

Commit
db7caa0374
Manifest
skills/git/commit-helper/SKILL.md
Scanned
1 file, 236 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 peopleforrester-commit-helper skill assists with creating Git commit messages. It can generate a draft commit message based on provided changes or refine an existing one to adhere to specific conventions. This helps ensure clear and consistent commit history for projects.

When to use it

  • Generating initial commit messages: When you've made several changes but aren’t sure how to best summarize them in a commit message.
  • Refining existing drafts: If you have a draft commit message that needs polishing or better alignment with project conventions.
  • Enforcing commit style guidelines: To ensure all commits adhere to a defined format (e.g., conventional commits).
  • Quickly creating concise messages: When needing to create short, descriptive commit messages for minor changes.

Key capabilities

  • Generates draft commit messages from change descriptions.
  • Refines existing commit message drafts.
  • Supports project-specific commit conventions (details not specified).

Example prompts

  • "Generate a commit message for these changes: Refactor user authentication module."
  • "Improve this commit message: 'Fixed bug'."
  • "Create a conventional commit based on the following changes: Add new feature X, breaking change to API endpoint Y."

Tips & gotchas

The skill's effectiveness depends on providing clear and concise descriptions of the changes being committed. While it can refine existing messages, understanding basic Git conventions will improve results.