commit-craft
Skill0 starsChanged 4 months agoMITView on GitHub
Turn a set of code changes, a diff, or a description of work done into clean Conventional Commits and, on request, a changelog entry. Use whenever the user asks for a commit message, says "write the commit", pastes a diff and wants it committed, asks to squash/split commits, or needs a CHANGELOG or release notes — even if they just describe what they changed in plain words.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Univers42/harness42their own version, first seen Nov 1, 2026
- milad-ahmd/agent-skillstheir own version, first seen Nov 1, 2026
- Univers42/claude-deal-with-the-deviltheir own version, first seen Oct 4, 2026
- moriwo-dev-ai/amateras-registrytheir own version, first seen Jul 26, 2026
- ccpowerpack/claude-code-skillstheir own version, first seen Jul 3, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- milad-ahmd/agent-skills★ 5same name
- Univers42/claude-deal-with-the-devil★ 4same name
- Univers42/harness42★ 4same name
- ccpowerpack/claude-code-skills★ 0same name
- moriwo-dev-ai/amateras-registry★ 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 repository8 other files it gives its agents.
- inbox-triageSkill
- incident-postmortemSkill
- landing-copySkill
- meeting-to-actionsSkill
- newsletter-forgeSkill
- pr-review-guardianSkill
- social-repurposeSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
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 30
If a diff mixes concerns (a feat + an unrelated fix), recommend splitting into separate commits and draft both — do not bury a fix inside a …
- Distinctive: line 59
Default: emit the commit message in a fenced block, ready to paste.
“Common” is measured: kept by at least 6 in 10 of the 5 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 Craft
Produce commit messages that are greppable, machine-parseable (Conventional Commits), and honest about scope. A good commit tells a future maintainer why, not just what.
Conventional Commit format
<type>(<scope>): <subject>
<body>
<footer>- type (required):
feat,fix,refactor,perf,docs,test,build,ci,chore,style,revert. - scope (optional): the module/area touched, lowercase (
auth,api,parser). - subject: imperative mood, no trailing period, ≤50 chars. "add" not "added"/"adds".
- body (optional): wrap at 72 cols. Explain motivation and contrast with previous behavior. Omit for trivial changes.
- footer:
BREAKING CHANGE: <desc>and/or issue refs (Closes #123).
Rules for choosing type
- Bug in existing behavior →
fix. New capability →feat. Neither, and no behavior change →refactor/chore. - A change that alters an API contract → append
!after type/scope AND aBREAKING CHANGE:footer. - If a diff mixes concerns (a feat + an unrelated fix), recommend splitting into separate commits and draft both — do not bury a fix inside a feature commit.
Subject line examples
Input: rewrote the token refresh so it retries on 401
Output: fix(auth): retry token refresh on 401 response
Input: added a config flag to disable telemetry
Output: feat(config): add flag to disable telemetry
Input: renamed variables and reformatted the parser, no logic change
Output: refactor(parser): rename variables for clarity
Changelog / release notes (on request)
Group commits under Keep-a-Changelog headings, newest first:
## [x.y.z] - YYYY-MM-DD
### Added <- feat
### Changed <- refactor/perf with user-visible effect
### Fixed <- fix
### Deprecated / Removed / Security <- as applicableRewrite each line for a reader of the product, not a reader of the code: drop internal scopes, keep the outcome. Flag every BREAKING CHANGE at the top under a bold ⚠ Breaking.
Output
Default: emit the commit message in a fenced block, ready to paste. If multiple commits are warranted, number them and give each its own block. Add no commentary unless asked why you split them.
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.