commit-message
Skill0 starsChanged 3 months agoMITView on GitHub
Use when the user is about to commit, asks for a commit message, or asks what to call a change.
62 other projects use a version of this.
Adopted by
Most recently taken up by
- AcademySoftwareFoundation/OpenImageIOtheir own version, first seen Nov 9, 2026
- haiderstudio/commit-message-skilltheir own version, first seen Nov 8, 2026
- mab-go/xmind-mcptheir own version, first seen Nov 8, 2026
- danielvm-git/bigpowerstheir own version, first seen Nov 6, 2026
- drinkspiller/skillstheir own version, first seen Nov 6, 2026
- mattiacerutti/supernovatheir own version, first seen Nov 2, 2026
Used with
Projects with it also use changelog, refactor and 7 more.
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.
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 3 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 3 projects that use this
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 3 projects that use this
OpenAISkillbrainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Also in 3 projects that use this
- GoogleSkill
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 3 projects that use this
MicrosoftSkillgrill-with-docs
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Also in 3 projects that use this
- +1 more from google
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- zulip/zulip★ 26ksame name
- mergisi/awesome-openclaw-agents★ 4.1ksame name
- AltraMayor/f3★ 3.4ksame name
- github/copilot-cli-for-beginners★ 2.9ksame name
- AcademySoftwareFoundation/OpenImageIO★ 2.4ksame name
- sheshbabu/zen★ 1.2ksame name
- s-kostyaev/ellama★ 963same name
- tektoncd/operator★ 606same name
- danielvm-git/bigpowers★ 288same name
- rshdhere/vibecheck★ 213same name
52 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 repository11 other files it gives its agents.
- api-docsSkill
- code-reviewSkill
- debug-loopSkill
- explain-this-fileSkill
- onboarding-mapSkill
- perf-passSkill
- pr-descriptionSkill
- refactor-safelySkill
- security-passSkill
- sql-reviewSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
9
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
- Distinctive: line 8
Write one conventional commit message from the staged diff.
- Distinctive: line 12
Run git diff --staged --stat to see the shape of the change.
- Distinctive: line 13
If the stat is empty, stop and tell the user nothing is staged.
- Distinctive: line 14
Run git diff --staged and read it.
- Distinctive: line 17
Write the subject in the imperative mood, under 52 characters, no trailing period.
- Distinctive: line 18
Add a body only when the reason for the change is not visible in the diff.
- Very specific: line 19
Add BREAKING CHANGE: or Closes #n footers only when the diff or the user gave you the fact.
- Distinctive: line 23
Never write vague subjects like "update stuff" or "various fixes".
- Distinctive: line 24
Never invent an issue number, a ticket id or a reviewer.
- Distinctive: line 25
Never mention the tool that wrote the message.
“Common” is measured: kept by at least 6 in 10 of the 51 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
Write one conventional commit message from the staged diff. Nothing else.
Procedure
- Run
git diff --staged --statto see the shape of the change. - If the stat is empty, stop and tell the user nothing is staged.
- Run
git diff --stagedand read it. Do not skim only filenames. - Classify the change into exactly one type: feat, fix, refactor, perf, docs, test, chore, build, ci. When two apply, pick the one a reader would care about most.
- Set the scope to the top level directory that holds most of the changed lines. Drop the scope if the change spans three or more unrelated areas.
- Write the subject in the imperative mood, under 52 characters, no trailing period.
- Add a body only when the reason for the change is not visible in the diff. Wrap at 72 columns.
- Add
BREAKING CHANGE:orCloses #nfooters only when the diff or the user gave you the fact.
Rules
- Never write vague subjects like "update stuff" or "various fixes".
- Never invent an issue number, a ticket id or a reviewer.
- Never mention the tool that wrote the message.
- Describe what the change does, not what files moved.
Output format
<type>(<scope>): <subject>
<optional body>
<optional footer>Print the message in a fenced block, then a single line offering to run the commit.
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.