agentleFS
godot-fungodot-fun/godot-agent/.agents/skills/git-commit-message/SKILL.md

git-commit-message

Skill202 starsChanged 11 days agoMITView on GitHub

Generate single-line Conventional Commits messages by analyzing git diffs and repository history. Use when the user asks for commit messages or help writing commits.

  • Reads credentials

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tdd.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    When inspecting changes for commit messages or change summaries:

    line 10
  2. Distinctive:

    Never run git diff --staged, git diff --cached, or git diff HEAD --cached

    line 13
  3. Distinctive:

    Never infer changes from git status "Changes to be committed"

    line 14
  4. Distinctive:

    Never warn about or analyze index vs working-tree mismatches from the staged list

    line 15
  5. Distinctive:

    If git diff HEAD is empty, there is nothing to commit — stop

    line 16
  6. Distinctive:

    When the user needs a commit message:

    line 20
  7. Distinctive:

    Read recent style: git log --oneline -15

    line 23
  8. Distinctive:

    Run status, diff, and log in parallel when possible.

    line 27
  9. Distinctive:

    Never: add a blank line or body paragraph after the subject.

    line 43
  10. Distinctive:

    Use existing scopes from recent commits when present

    line 63
  11. Very specific:

    Prefer short, stable names: auth, db, config, deps

    line 64
  12. Distinctive:

    Never include secrets (.env, credentials, tokens) in the commit

    line 87
  13. Distinctive:

    Do not run git commit unless the user explicitly requests it

    line 89

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

Rules

When inspecting changes for commit messages or change summaries:

  • Only git diff HEAD defines what changed (all local changes vs last commit)
  • Never run git diff --staged, git diff --cached, or git diff HEAD --cached
  • Never infer changes from git status "Changes to be committed"
  • Never warn about or analyze index vs working-tree mismatches from the staged list
  • If git diff HEAD is empty, there is nothing to commit — stop

Quick Start

When the user needs a commit message:

  1. Inspect changes: git status, git diff HEAD (all local changes vs last commit)
  2. Read recent style: git log --oneline -15
  3. Draft a single-line Conventional Commits message matching repo conventions
  4. Return the message only — do not commit unless explicitly asked

Run status, diff, and log in parallel when possible.

Message Format

Single line only — no body:

<type>[<scope>]: <subject>
PartRules
typeRequired. One of: feat, fix, refactor, docs, test, chore, perf, ci, build, style, revert
scopeOptional. Module or area in square brackets (e.g. [auth], [api], [ui]). Omit brackets entirely if unclear
subjectImperative mood, lowercase, no trailing period, ≤72 chars. Must stand alone — pack intent into this line

Never add a blank line or body paragraph after the subject.

Type Selection

TypeWhen
featNew user-facing capability
fixBug fix
refactorCode change without behavior change
docsDocumentation only
testTests only
choreMaintenance, deps, tooling
perfPerformance improvement
ciCI/CD config
buildBuild system or external deps
styleFormatting, whitespace (no logic change)
revertRevert a prior commit

Scope Guidelines

  • Use existing scopes from recent commits when present
  • Prefer short, stable names: auth, db, config, deps
  • Drop scope rather than guess incorrectly

Workflow

Task Progress:
- [ ] Run git status + `git diff HEAD`
- [ ] Read recent git log for style alignment
- [ ] Identify primary change type and scope
- [ ] Draft single-line subject (imperative, self-contained)
- [ ] Check for secrets or files that should not be committed
- [ ] Present message to user

Split vs Single Commit

  • One logical change → one commit
  • Unrelated changes (feat + fix in different areas) → suggest splitting
  • Large refactor + feature → suggest separate commits

Safety

  • Never include secrets (.env, credentials, tokens) in the commit
  • Warn if changed files look sensitive
  • Do not run git commit unless the user explicitly requests it

Output

Present exactly one line in a copy-paste block:

feat[auth]: add jwt token refresh endpoint
fix[ui]: prevent double submit on checkout form

CLI

Copy-paste commands: cli/git-commit-message.md

Additional Resources

  • More examples: examples.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.