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
- artivilla/agent-skillstheir own version, first seen Nov 8, 2026
- godot-fun/gaiword for word, first seen Nov 1, 2026
- sbrudz/agent-skillstheir own version, first seen Nov 1, 2026
- cathaysia/skillstheir own version, first seen Oct 23, 2026
- shy-UCAS/claude-skillstheir own version, first seen Oct 20, 2026
- murongg/skillstheir own version, first seen Oct 20, 2026
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.
GoogleSkilltdd
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
Other versions22 projects use a version of this.
Word for word · 1
- godot-fun/gai★ 202100% same
Edited · 0
None found.
Wrote their own version · 21
- AkimioJR/AutoFilm★ 1.1ksame name
- overflow65537/MAA_Punish★ 384same name
- 535803710/ai-rd-skills★ 8same name
- cathaysia/skills★ 2same name
- host452b/polish★ 2same name
- sbrudz/agent-skills★ 2same name
- alapha888/agent-skills-en★ 1same name
- ankitgoyalio/skills★ 1same name
- bat-in-metropolis/git-commit-message-skill★ 1same name
- langliu/skills★ 1same name
11 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- ai-text-to-speechSkill
- audio-denoiseSkill
- audio-fadeSkill
- audio-loudness-normalizationSkill
- audio-sample-rate-standardizeSkill
- audio-splitSkill
- audio-to-oggSkill
- audio-to-textSkill
- audio-to-wavSkill
- audio-trimSkill
- audio-volume-adjustSkill
- file-naming-normalizationSkill
- image-inpaint-regionSkill
- image-region-remove-key-color-appSkill
- image-remove-backgroundSkill
- image-remove-white-backgroundSkill
- image-resizeSkill
- image-sprite-sheet-splitSkill
- image-to-pngSkill
- image-to-textSkill
- image-trimSkill
- storyboard-av-mixSkill
- storyboard-shot-to-htmlSkill
- storyboardSkill
- storyboard-ttsSkill
- video-4k-normalizationSkill
- video-compress-to-sizeSkill
- video-merge-gpuSkill
- video-mergeSkill
- video-publishSkill
- video-remove-audioSkill
- video-to-4kSkill
- video-to-60fpsSkill
- video-to-ogvSkill
- video-to-wavSkill
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
- Distinctive: line 10
When inspecting changes for commit messages or change summaries:
- Distinctive: line 13
Never run git diff --staged, git diff --cached, or git diff HEAD --cached
- Distinctive: line 14
Never infer changes from git status "Changes to be committed"
- Distinctive: line 15
Never warn about or analyze index vs working-tree mismatches from the staged list
- Distinctive: line 16
If git diff HEAD is empty, there is nothing to commit — stop
- Distinctive: line 20
When the user needs a commit message:
- Distinctive: line 23
Read recent style: git log --oneline -15
- Distinctive: line 27
Run status, diff, and log in parallel when possible.
- Distinctive: line 43
Never: add a blank line or body paragraph after the subject.
- Distinctive: line 63
Use existing scopes from recent commits when present
- Very specific: line 64
Prefer short, stable names: auth, db, config, deps
- Distinctive: line 87
Never include secrets (.env, credentials, tokens) in the commit
- Distinctive: line 89
Do not run git commit unless the user explicitly requests it
“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.
Files
Git Commit Message
Rules
When inspecting changes for commit messages or change summaries:
- Only
git diff HEADdefines what changed (all local changes vs last commit) - Never run
git diff --staged,git diff --cached, orgit 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 HEADis empty, there is nothing to commit — stop
Quick Start
When the user needs a commit message:
- Inspect changes:
git status,git diff HEAD(all local changes vs last commit) - Read recent style:
git log --oneline -15 - Draft a single-line Conventional Commits message matching repo conventions
- 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>| Part | Rules |
| type | Required. One of: feat, fix, refactor, docs, test, chore, perf, ci, build, style, revert |
| scope | Optional. Module or area in square brackets (e.g. [auth], [api], [ui]). Omit brackets entirely if unclear |
| subject | Imperative 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
| Type | When |
feat | New user-facing capability |
fix | Bug fix |
refactor | Code change without behavior change |
docs | Documentation only |
test | Tests only |
chore | Maintenance, deps, tooling |
perf | Performance improvement |
ci | CI/CD config |
build | Build system or external deps |
style | Formatting, whitespace (no logic change) |
revert | Revert 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 userSplit 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 commitunless the user explicitly requests it
Output
Present exactly one line in a copy-paste block:
feat[auth]: add jwt token refresh endpointfix[ui]: prevent double submit on checkout formCLI
Copy-paste commands: cli/git-commit-message.md
Additional Resources
- More examples: examples.md
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
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.

