commit-discipline
Skill1 starsChanged 3 months agoMITView on GitHub
Plan implementation work into small test-gated Git commits and record each stage through commit-discipline-mcp.
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
- dfedoryshchev/weftworkstheir own version, first seen Oct 13, 2026
- applypack/applypacktheir own version, first seen Aug 27, 2026
- zaidmukaddam/skillstheir own version, first seen Aug 17, 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
- dfedoryshchev/weftworks★ 5same name
- robinbril/claude-code-harness★ 3same 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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for implementation work that should be split into reviewable commits.
- Very specific: line 10
Before editing, call plan_task with 2-4 ordered stages and exact repository-relative files.
- Very specific: line 12
Call commit_stage for the current stage instead of running git commit directly.
- Very specific: line 13
Check task_status before moving to the next stage.
- Very specific: line 14
Call finish_task only after every stage is committed and the worktree is clean.
- Distinctive: line 16
Never use this tool to push, rewrite history, or bypass failing tests.
“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
Use this skill for implementation work that should be split into reviewable commits.
- Before editing, call
plan_taskwith 2-4 ordered stages and exact repository-relative files. - Work only on the current stage's declared files.
- Call
commit_stagefor the current stage instead of runninggit commitdirectly. - Check
task_statusbefore moving to the next stage. - Call
finish_taskonly after every stage is committed and the worktree is clean.
Never use this tool to push, rewrite history, or bypass failing tests.
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.