commit-msg
Skill0 starsChanged 2 months agoMITView on GitHub
Draft a conventional commit message for the currently staged diff. Prompt-only — reads the diff and $ARGUMENTS (an optional scope hint), writes nothing.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- Eclipter/agentstheir 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 implement, research and 3 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.
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 3 projects that use this
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
- Eclipter/agents★ 1same name
- eyeix/skills★ 1same name
- laonzh/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 repository3 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- new-componentSkill
- review-securitySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
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
- Very specific: line 14
Run git diff --staged and git status --short.
- Very specific: line 17
If $ARGUMENTS gives a scope, use it.
- Distinctive: line 20
Add a body only if the diff needs one sentence of "why" beyond the summary.
“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
Run git diff --staged and git status --short. From the staged diff, write one
conventional commit message: type(scope): summary, types feat|fix|docs|chore|test|refactor.
- If
$ARGUMENTSgives a scope, use it; otherwise infer one from the changed paths (cli,api,store,test,docs). - Summary line under 72 characters, imperative mood ("add", not "added").
- Add a body only if the diff needs one sentence of "why" beyond the summary.
- Print the message only — do not run
git 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.