commit-message-generator
Skill0 starsChanged 7 days agoMITView on GitHub
Generate a clear, concise conventional commit message from staged code changes. Use when writing a commit message.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kanopi/cms-cultivatortheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kanopi/cms-cultivator★ 17same 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 repository14 other files it gives its agents.
- docxSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- code-review-seniorSkill
- explain-in-vietnamesesSkill
- implement-leaf-ticketSkill
- security-auditSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read the staged diff and write one conventional commit message:
- Distinctive: line 19
body: only when the change spans several areas or the why isn't obvious.
- Distinctive: line 25
No file paths, line numbers or code.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Commit Message Generator
Read the staged diff and write one conventional commit message:
type(scope): subject
- Optional bullet.- type:
feat,fix,refactor,perf,style,docs,testorchore. - scope: the main area touched, ideally one word (
auth,api,ui). - subject: imperative, lowercase, no period, at most 50 characters.
- body: only when the change spans several areas or the why isn't obvious. Give 2–5 one-line bullets (max 72 characters), each a capitalized imperative verb ending with a period, saying what changed, not how.
Rules:
- Give one message only, not a list of options. If the diff mixes unrelated changes, describe the main one.
- No file paths, line numbers or code.
- A teammate should get it in 5 seconds. When in doubt, go shorter.
Example:
feat(auth): add biometric login
- Add fingerprint and face unlock on the sign-in screen.
- Store the refresh token in secure storage.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.