Skip to content
TrustedSkillsbeta
Back to all skills

Commit Helper

Checked
charon-fan·vlatest·backend·MIT

This "Commit Helper" assists developers by suggesting descriptive commit messages and ensuring best practices for clearer code history.

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 zhaono1/agent-playbook --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

charon-fan

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 charon-fan/agent-playbook at be7a9d7d17.

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

Commit
be7a9d7d17
Manifest
skills/commit-helper/SKILL.md
Scanned
6 files, 504 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 charon-fan-commit-helper skill assists in crafting effective Git commit messages. It can generate a well-formatted commit message based on provided changes or descriptions, ensuring clarity and adherence to best practices. This helps streamline the development workflow and improves code maintainability by creating consistent and informative commit history.

When to use it

  • Generating initial commit messages: When you've made several changes but are unsure how to summarize them concisely.
  • Ensuring proper formatting: To automatically format commit messages according to a specific style guide or convention.
  • Documenting complex changes: For larger commits, the skill can help articulate the purpose and scope of the modifications.
  • Improving team consistency: To standardize commit message structure across a development team.

Key capabilities

  • Generates Git commit messages based on provided context.
  • Supports various formatting conventions for commit messages.
  • Aids in summarizing changes made to code.

Example prompts

  • "Generate a commit message for these changes: fixed bug in user authentication."
  • "Create a formatted commit message describing the refactor of the payment processing module."
  • “Write a commit message following conventional commits format for this change: feat(api): add endpoint for retrieving product details”

Tips & gotchas

The skill's effectiveness depends on providing clear and concise information about the changes being committed. While it can generate messages, reviewing and potentially refining them is always recommended to ensure accuracy and completeness.