commit-msg
Skill1 starsChanged 4 days agoMITView on GitHub
Write the commit message. Do not stage, commit, or push unless the same message explicitly asks for a commit.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- codechup/claude-code-labtheir own version, first seen Nov 8, 2026
- cykedev/vereinsheimtheir own version, first seen Nov 3, 2026
- huntie/skillstheir own version, first seen Nov 1, 2026
- 5hseok/hanipman-gatetheir own version, first seen Oct 20, 2026
- AlaaMousa05/billtheir own version, first seen Oct 15, 2026
- eyeix/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use research, code-review and 2 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.
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 4 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- NG-ZORRO/ng-zorro-antd★ 9.2ksame name
- yaklang/yakit★ 7.9ksame name
- rust-works/succinctly★ 52same name
- Akindu23/my-agent-skills★ 4same name
- jenreh/appkit★ 4same name
- couimet/my-claude-skills★ 1same name
- cykedev/vereinsheim★ 1same name
- eyeix/skills★ 1same name
- laonzh/skills★ 1same name
- psw7205/skills★ 1same name
6 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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- broSkill
- create-my-skillSkill
- glassmorphismSkill
- swiftui-designSkill
- humanizerSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- clean-up-git-historySkill
- diagnoseSkill
- fixSkill
- grill-meSkill
- implementSkill
- loopSkill
- subagentsSkill
- update-docsSkill
- verify-appSkill
- sudo-ssh-authSkill
- web-app-secSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
2
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 16
If git log fails because the repository has no commits yet, skip the log and use the default language and format.
- Very specific: line 17
If a diff is larger than about 2000 lines, read --stat and sample the key files instead of the whole diff.
- Distinctive: line 21
Do not quote secrets, tokens, or private keys.
- Very specific: line 41
Add a scope in parentheses only when the repository already does, or when the subject is ambiguous without it.
“Common” is measured: kept by at least 6 in 10 of the 12 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-msg
What to inspect
From the repository root, in parallel:
git status --shortgit diff --cachedandgit diff --cached --statgit diffandgit diff --stat, when the index is empty or unstaged changes remaingit log -20 --format='%s%n%b%n---'- If
git logfails because the repository has no commits yet, skip the log and use the default language and format. - If a diff is larger than about 2000 lines, read
--statand sample the key files instead of the whole diff.
A repository commit convention (CONTRIBUTING, commitlint, .gitmessage) overrides the rules below.
Do not quote secrets, tokens, or private keys. If they appear in the diff, say they must not be committed and do not describe them as a normal change.
What the message covers
- Non-empty index: describe only staged changes. In one line, name what remains unstaged and will not be in this commit.
- Empty index: describe the working tree and say that nothing is staged.
- Several independent changes: one message per atomic commit, in apply order. Do not merge them into one.
Format
Take the language and shape from recent commits when the style is consistent. Otherwise use English and Conventional Commits:
type: imperative summary
Why this exists, only when the subject does not already say it.type: feat, fix, refactor, perf, docs, test, build, ci, chore, style, revert.
Add a scope in parentheses only when the repository already does, or when the subject is ambiguous without it. A breaking change uses type!: and a BREAKING CHANGE: trailer.
Subject line:
- imperative mood, as a continuation of "If applied, this commit will …";
- the change to the system, not a file list and not "update code";
- no trailing period;
- the whole line at most 50 characters, even when recent subjects are longer (hard limit);
- something that belongs in a changelog.
Add a body only when the "why" is not obvious from the subject. One blank line between the subject and the body is required. Keep each body line under 72 characters when a break is possible (soft limit). Do not retell the diff and do not write "this commit".
Trailers only when they are real: BREAKING CHANGE:, Fixes #n, Refs #n. Do not invent issue numbers.
Reply
First, one line: staged, the whole tree, or several commits. Then each message in its own fenced block, ready to paste into git commit. Nothing else.
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.