Index of every page on this site: llms.txt
All skills
Run it yourself

Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing commits.

Use this Skill: https://skilld.dev/gh/nodnarbnitram/claude-code-extensions/commit-helper

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈39 tokens for metadata: the name and description. ≈283 when used: this file.

Description uses 2.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈158 characters, or 2.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Commit Helper

Generate well-structured commit messages following conventional commit format.

Instructions

  1. Run git diff --staged to see staged changes
  2. Analyze the changes to understand:
    • What files were modified
    • What type of change (feat, fix, refactor, docs, etc.)
    • The scope/component affected
  3. Generate a commit message with:
    • Summary line under 50 characters
    • Type prefix (feat, fix, docs, refactor, test, chore)
    • Optional scope in parentheses
    • Detailed body explaining what and why

Commit Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • refactor: Code restructuring without behavior change
  • test: Adding or updating tests
  • chore: Maintenance tasks

Best Practices

  • Use present tense ("Add feature" not "Added feature")
  • Explain what and why, not how
  • Keep summary concise but descriptive
  • Reference issue numbers when applicable

Example Output

feat(auth): add OAuth2 support for GitHub login

- Implement OAuth2 flow with PKCE
- Add token refresh mechanism
- Store tokens securely in encrypted storage

Closes #123

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo4 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is safe to use for generating commit messages. It analyzes local git changes to provide well-structured message suggestions. The only minor risk identified is the potential for the agent to be influenced by instructions hidden within the code it reads, as it lacks clear boundaries for processing untrusted code data.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • Runlayer9mo

    1 file scanned · No issues

Signed by skilld at 35e7f7d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 8 months ago

README badge

README badge for nodnarbnitram/claude-code-extensions/commit-helper