git-discipline
Skill0 starsChanged 3 months agoMITView on GitHub
Use before starting work, after reaching any working state, at session end, and when the user asks to undo or go back — keeps every change recoverable and the history readable.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- modaal-agent/skillstheir own version, first seen Nov 15, 2026
- cobusgreyling/grok-build-arsenaltheir own version, first seen Nov 8, 2026
- curvedinf/dev-skillstheir own version, first seen Oct 20, 2026
- Confidence-huang/agent-git-disciplinetheir own version, first seen Oct 13, 2026
- Sapere-IA/sdd-onboarding-kittheir own version, first seen Oct 6, 2026
- devpilotX/skillstheir own version, first seen Sep 22, 2026
Used with
Projects with it also use security-audit.
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.
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- Sapere-IA/sdd-onboarding-kit★ 19same name
- annatchijova/SKILLS★ 9same name
- curvedinf/dev-skills★ 7same name
- cobusgreyling/grok-build-arsenal★ 6same name
- radif-ru/ai-multi-agent-system★ 6same name
- dekoza/oh-my-slop★ 4same name
- modaal-agent/skills★ 2same name
- AL-JANEF/janef-forge★ 1same name
- AL-JANEF/janefskills★ 1same name
- Confidence-huang/agent-git-discipline★ 0same name
4 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-ticketSkill
- creating-skillsSkill
- documentingSkill
- explaining-complexitySkill
- finding-knowledgeSkill
- journalingSkill
- start-boardSkill
- werkbank-work-ticketSkill
- work-ticketsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Commit at every working state — "working" means the project's own checks pass, not merely that the file was saved.
- Very specific: line 29
Never rewrite history: no reset --hard, no --amend (not even on the latest commit), no force anything.
- Distinctive: line 34
Only when they need to care.
“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
Git Discipline
The repo is local-only. Branches are an undo mechanism here, not a review mechanism. History is the backup — treat it that way.
Rules
mainis the working branch; commit directly for routine work.- Commit at every working state — "working" means the project's own checks pass, not merely that the file was saved. Small commits beat big ones.
- Message format: first line = what changed for the tool; body = why, when the why isn't obvious. English. Written so a future session — or a hired developer — can follow the history without asking anyone.
- Risky or experimental work: branch first (
git checkout -b try-<thing>), merge when it works. Abandoned experiment: journal it (what was tried, why abandoned —journalingskill), then delete the branch. (git branch -D— under the template's stock allowlist this shows a permission box by design; tell the user in one plain sentence what is being deleted and why before confirming.) - Docs, CHANGELOG and index updates go in the SAME commit as the change they describe.
- Session end = clean tree (
git statusshows nothing) and a journal entry. Genuinely half-done work: commit it on a branch namedwip-<thing>with a commit message startingwip:plus a journal entry saying exactly where it stands. - Never rewrite history: no
reset --hard, no--amend(not even on the latest commit), no force anything. A wrong commit is fixed by a new commit.
Explaining git to the user
Only when they need to care. "I save a snapshot after every change, so we can always go back" covers most conversations. Never make the user run git commands.
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.

