commit-message-writer
Skill0 starsChanged 4 months agoMITView on GitHub
Drafts a commit message from the currently staged diff, matching the repo's existing commit conventions. Use when the user asks to 'write a commit message', 'draft a commit message for this', or invokes /commit-message. Reads staged changes and recent git log to match style — never runs git commit or git add itself.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Lethe044/agentskill-kittheir own version, first seen Nov 1, 2026
- Laffey-82/cn-agent-skillstheir own version, first seen Aug 29, 2026
- bestdeejay-design/agent-skillstheir own version, first seen Aug 9, 2026
- bilals2008/bilal-skillstheir own version, first seen Jul 4, 2026
- RandyRawgust/ai-knowledge-base-templatetheir own version, first seen May 22, 2026
- sujithq/skillstheir own version, first seen May 20, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- Lethe044/agentskill-kit★ 48same name
- bestdeejay-design/agent-skills★ 6same name
- Laffey-82/cn-agent-skills★ 1same name
- RandyRawgust/ai-knowledge-base-template★ 1same name
- bilals2008/bilal-skills★ 0same name
- kakarot-oncloud/claude-dev-skills★ 0same name
- sujithq/skills★ 0same name
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 repository2 other files it gives its agents.
- dotnet-researchSkill
- pr-description-writerSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
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
- Very specific: line 17
Check recent history (git log -10 --oneline) to detect the repo's convention — conventional-commit prefixes (feat:/fix:/chore:/docs:), …
- Distinctive: line 18
If the staged diff spans clearly unrelated changes (touching separate features/modules with no shared purpose), flag it rather than …
- Distinctive: line 33
Don't fabricate an issue/ticket reference — only include one if it's clearly relevant (mentioned by the user, or present in the branch …
“Common” is measured: kept by at least 6 in 10 of the 6 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
Purpose
Draft a commit message for changes the user has already staged, grounded in the actual diff and the repo's existing conventions, so writing the commit isn't a separate manual step.
Trigger
/commit-message, or phrasing like "write a commit message", "draft a commit message for this", "what should the commit message be". If nothing is staged, ask whether to use unstaged changes or which files to include — don't guess.
Gather
- Inspect what's staged:
git diff --staged --statand the fullgit diff --stagedfor substance, not just file names. - Check recent history (
git log -10 --oneline) to detect the repo's convention — conventional-commit prefixes (feat:/fix:/chore:/docs:), imperative vs. past tense, typical subject line length, whether body paragraphs are used at all. - If the staged diff spans clearly unrelated changes (touching separate features/modules with no shared purpose), flag it rather than papering over it with a vague message — that's usually a sign the changes belong in separate commits.
Write
- Subject line — imperative mood ("Add X", "Fix Y", not "Added"/"Adds"), matching the repo's length convention and prefix style if one is established.
- Body — only if the change needs more than the subject to explain itself: a short paragraph or bullets on why, not a restatement of the diff. Skip it entirely for small, self-explanatory changes.
Voice
Plain and specific, weighted toward why over what — the diff already shows what changed. No "This commit does the following:" framing, no filler.
Ground rules
- Drafts message text only — never runs
git commit,git add, or any other git write operation. - Works from staged changes by default; only considers unstaged changes if the user explicitly asks.
- Don't fabricate an issue/ticket reference — only include one if it's clearly relevant (mentioned by the user, or present in the branch name).
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.