Skip to content
TrustedSkillsbeta
Back to all skills

Commit Helper

Checked
tzuchaine·vlatest·backend

This "Commit Helper" suggests improved commit messages based on your code changes, streamlining workflows and boosting code quality.

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 tzuchaine/ai-skills --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

tzuchaine

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 tzuchaine/ai-skills at a9525ba4b3.

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

Commit
a9525ba4b3
Manifest
commit-helper/SKILL.md
Scanned
2 files, 427 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 tzuchaine-commit-helper skill assists with generating Git commit messages. It can analyze changes, suggest concise summaries, and format commits according to established conventions. This helps ensure a clear and consistent project history for developers.

When to use it

  • You need help crafting effective commit messages when making code changes.
  • You want to enforce a specific commit message style within your team or project.
  • You're working on a large pull request and want to generate a summary of the changes.
  • You are unsure how to best describe the changes you made in a concise manner.

Key capabilities

  • Generates commit summaries based on code diffs.
  • Supports formatting commits according to conventions.
  • Provides suggestions for concise descriptions.

Example prompts

  • "Summarize these changes into a git commit message." (followed by the diff)
  • "Generate a commit message for this pull request." (with link to PR)
  • "Format this commit message: 'Fixes bug'"

Tips & gotchas

The skill's effectiveness depends on providing clear and concise code changes. It is best used in conjunction with version control systems like Git.