commit-discipline
Skill5 starsChanged 2 months agoMITView on GitHub
small, single-purpose commits with honest messages
5 other projects use a version of this.
Adopted by
Most recently taken up by
- robinbril/claude-code-harnesstheir own version, first seen Nov 1, 2026
- whoaskedssselery/claude-workspacetheir own version, first seen Oct 20, 2026
- applypack/applypacktheir own version, first seen Aug 27, 2026
- zaidmukaddam/skillstheir own version, first seen Aug 17, 2026
- ayush-singh-0601/commit-discipline-mcptheir own version, first seen Aug 11, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- applypack/applypack★ 30same name
- zaidmukaddam/skills★ 18same name
- robinbril/claude-code-harness★ 3same name
- ayush-singh-0601/commit-discipline-mcp★ 1same name
- whoaskedssselery/claude-workspace★ 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.
- agent-budgetSkill
- code-reviewSkill
- dependency-checkSkill
- eval-before-mergeSkill
- incident-reviewSkill
- plan-firstSkill
- safe-refactorSkill
- test-firstSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
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 10
never commit code you can't explain.
“Common” is measured: kept by at least 6 in 10 of the 4 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-discipline
- one logical change per commit.
- the message says what changed and why, not how.
- never commit code you can't explain.
- stage explicit paths, not everything at once.
atomic vs batch
default to atomic - one change, one commit. batch only when the pieces are meaningless apart (a rename across ten files, a mechanical format pass). if a reviewer would want to look at one piece on its own, it is its own 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.