agentleFS
Sign inStart free
nodnarbnitramnodnarbnitram/claude-code-extensions/.claude/skills/commit-helper/SKILL.md

commit-helper

Skill16 starsChanged 7 months agoMITView on GitHub

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

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run git diff --staged to see staged changes

    line 12
  2. Distinctive:

    Use present tense ("Add feature" not "Added feature")

    line 34
  3. Distinctive:

    Keep summary concise but descriptive

    line 36

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free