git-change-control
Skill1 starsChanged 4 days agoMITView on GitHub
Use when staging, committing, amending, rebasing, cherry-picking, resolving conflicts, updating nested repositories or gitlinks, pushing rewritten history, or auditing Git scope in a shared or dirty checkout. Preserve unrelated work, prove task ownership, and verify recorded history; do not use for ordinary read-only code inspection.
In this repository21 other files it gives its agents.
- animation-vocabularySkill
- apple-chartsSkill
- apple-hig-componentsSkill
- apple-hig-foundationsSkill
- apple-hig-getting-startedSkill
- apple-hig-inputsSkill
- apple-hig-patternsSkill
- apple-hig-technologiesSkill
- apple-sheetsSkill
- batch-commitSkill
- fluid-interface-designSkill
- improve-animationsSkill
- marketing-art-directionSkill
- marketing-product-mediaSkill
- marketing-reference-forensicsSkill
- marketing-visual-qaSkill
- message-delivery-integritySkill
- production-verificationSkill
- product-marketing-personasSkill
- security-auditSkill
- systems-builder-writingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
Treat an unexplained change as someone else's work.
- Distinctive: line 19
Do not discard, reset, overwrite, or unstage changes you did not create.
- Distinctive: line 20
If a task-owned file also contains unrelated edits, isolate owned hunks.
- Distinctive: line 21
Follow the repository's established subject, scope, authorship, and signing policy.
- Distinctive: line 22
Keep materially separate changes in separate commits when their ownership, review, rollback, or release paths differ.
- Distinctive: line 27
Before reporting a history operation complete, verify the recorded paths, subject, author, signature when required, and remaining checkout …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Git Change Control
Treat an unexplained change as someone else's work. A request to commit authorizes committing the task-owned change; it does not authorize including unrelated work, rewriting history, pushing, or changing nested repositories outside the task.
Route the work
- For an ordinary commit, commit audit, or commit-splitting request, read references/commits.md.
- For rebases, cherry-picks, conflict resolution, force pushes, nested repositories, or gitlink updates, also read references/history-and-nested-repositories.md.
Invariants
- Inspect
git status --shortbefore editing and again before staging. - Build an explicit allowlist of task-owned files or hunks. Never use
git add .,git add -A, broad path globs, or destructive cleanup merely to make the checkout look tidy. - Do not discard, reset, overwrite, or unstage changes you did not create. Work around unrelated staged entries instead of disturbing them.
- If a task-owned file also contains unrelated edits, isolate owned hunks. If exact isolation cannot be proven, stop before committing that file and report the ambiguity.
- Follow the repository's established subject, scope, authorship, and signing policy. Do not invent a new convention during an unrelated task.
- Keep materially separate changes in separate commits when their ownership, review, rollback, or release paths differ.
- A commit is not a push. A push is not a build. A build is not a deployment. Report each state separately.
Completion standard
Before reporting a history operation complete, verify the recorded paths, subject, author, signature when required, and remaining checkout state. State the commit SHA or affected range, validation performed, exact scope, and whether unrelated changes remain.
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.

