commit-message-writer
Skill1 starsChanged 6 months agoMITView on GitHub
Draft a conventional commit message from the staged git diff. Use before any commit when the user asks you to write the message or generate one. Triggers: commit message, write a commit msg, generate commit, what should I commit this as.
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
- michaelm7456/claude-skillstheir own version, first seen Jul 19, 2026
- bilals2008/bilal-skillstheir own version, first seen Jul 4, 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
- bilals2008/bilal-skills★ 0same name
- kakarot-oncloud/claude-dev-skills★ 0same name
- michaelm7456/claude-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 repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- brainstormSkill
- compile-topicSkill
- course-builderSkill
- daily-note-writerSkill
- deck-builderSkill
- diagnoseSkill
- drift-fixSkill
- forgeSkill
- git-bootstrapSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- lesson-content-writerSkill
- project-scaffolderSkill
- prototypeSkill
- retroSkill
- reviveSkill
- setup-pre-commitSkill
- specialist-creatorSkill
- sweep-inboxSkill
- tddSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- workflow-authorSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run git diff --staged --stat to see scope
- Distinctive: line 13
Run git diff --staged to see actual changes
- Very specific: line 24
Write a one-liner: <type>(<scope>): <imperative present-tense summary>
- Distinctive: line 34
Don't write "Updated X" - use imperative present: "update X"
- Distinctive: line 35
Don't add a period at the end of the subject line
- Distinctive: line 36
Don't reference internal session details Andy wouldn't want public
- Very specific: line 37
Don't lie about scope if changes span multiple areas - use misc or split commits
“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
Commit Message Writer
When to use
User about to commit, asks for a message. Or you're about to commit on their behalf and need to draft one.
Process
- Run
git diff --staged --statto see scope - Run
git diff --stagedto see actual changes - Identify the type:
feat- new featurefix- bug fixdocs- documentation onlyrefactor- code change, no behavior changestyle- formatting, whitespacetest- test additions or fixeschore- build, deps, configperf- performance
- Identify the scope (e.g.
cc,vault,snake,hooks,agents) - Write a one-liner:
<type>(<scope>): <imperative present-tense summary> - First line max 72 chars. If more context needed, blank line + body.
Examples
feat(cc): add script output dialog with stdout/stderr capturefix(snake): revert sprite-sheet to static PNG after animation glitchesdocs(roadmap): mark phase 10 complete, refresh status headerchore(vault): propagate <YOUR-GH-HANDLE> GitHub handle to 5 dept-head memories
Don't
- Don't write "Updated X" - use imperative present: "update X"
- Don't add a period at the end of the subject line
- Don't reference internal session details Andy wouldn't want public
- Don't lie about scope if changes span multiple areas - use
miscor split commits
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.