agentleFS
Sign inStart free
roborracleroborracle/agent-workflow-kit/skills/git-commit-helper/SKILL.md

git-commit-helper

Skill0 starsChanged 3 months agoMITView on GitHub

Create properly formatted, detailed commit messages following Conventional Commits specification. Use when committing changes, preparing commits, or when user needs help with commit message best practices.

14 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 9 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:

    Create clear, detailed commit messages following Conventional Commits specification.

    line 9
  2. Distinctive:

    Check staged changes: git diff --staged

    line 36
  3. Distinctive:

    Use imperative mood ("Add feature" not "Added feature")

    line 42

“Common” is measured: kept by at least 6 in 10 of the 9 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

Git Commit Helper

Create clear, detailed commit messages following Conventional Commits specification.

Commit Message Format

<type>(<scope>): <description>

[optional body]

[optional footer]

Commit Types

TypeUse For
featNew features
fixBug fixes
docsDocumentation changes
styleCode style (formatting, semicolons)
refactorCode refactoring without feature changes
perfPerformance improvements
testAdding or updating tests
choreMaintenance tasks
buildBuild system or dependency changes
ciCI configuration changes
revertReverting previous commits

Analysis Workflow

  1. Check staged changes: git diff --staged
  2. Review recent commits for style: git log --oneline -10
  3. Analyze: What changed? Why? Impact on users? Breaking changes? Related issues?

Message Guidelines

  • Subject line ≤72 characters (soft limit, per rules/git-workflow.md); shorter is better when it still says what changed
  • Use imperative mood ("Add feature" not "Added feature")
  • Separate subject from body with blank line
  • Wrap body at 72 characters
  • Explain what and why, not how

Examples

feat(auth): add JWT token validation

Implement token validation middleware for protected routes.
Tokens expire after 24 hours and require refresh.

Closes #123
feat(api)!: change user endpoint response format

BREAKING CHANGE: User endpoint now returns nested address object
instead of flat address fields.

Closes #789

Pre-Commit Checklist

  • Changes are staged (git add)
  • Tests pass
  • Linting passes
  • Type checking passes
  • Commit message follows format
  • Related issues referenced

Additional Resources

  • For detailed commit message examples (features, fixes, breaking changes, refactors, performance), see examples/commit-messages.md

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