Skip to content
TrustedSkillsbeta
Back to all skills

Commit Helper

Checked
nodnarbnitram·vlatest·backend·MIT

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

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 nodnarbnitram/claude-code-extensions --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

nodnarbnitram

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 nodnarbnitram/claude-code-extensions at 35e7f7deae.

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

Scanned
2 files, 96 lines
Copies in repo
2 — all of them scanned
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 commit-helper skill assists with generating Git commit messages. It can analyze code changes and automatically create a concise, descriptive commit message based on the modifications. This helps streamline development workflows and ensures consistent commit history. The skill is designed to be used with Claude Code extensions.

When to use it

  • You've made several changes to a codebase and want a well-formatted commit message quickly.
  • You’re working in a team that requires standardized commit messages.
  • You are unsure how to best describe the changes you have made.
  • You need to generate a commit message for a pull request.

Key capabilities

  • Analyzes code diffs
  • Generates descriptive commit messages
  • Supports standard commit conventions (implied)
  • Integrates with Claude Code extensions

Example prompts

  • "Generate a commit message for these changes: [paste diff]"
  • "Create a commit message summarizing the following modifications to src/main.py: [paste code]"
  • “Write a short, descriptive commit message based on this pull request.”

Tips & gotchas

The skill's effectiveness depends on the clarity and structure of the provided code diff or changes. Providing context about the purpose of the changes can improve the quality of the generated commit messages.