implem-brake
Skill1 starsChanged 16 days agoMITView on GitHub
Withhold or restore permission to modify code, on the user's explicit signal.
In this repository15 other files it gives its agents.
- audit-skill-runSkill
- challenge-handoffSkill
- dot-diagramsSkill
- handoffSkill
- resume-handoffSkill
- review-auto-loopSkill
- review-correctnessSkill
- review-docsSkill
- review-judgeSkill
- review-readabilitySkill
- review-testsSkill
- rust-project-maintenanceSkill
- settle-discussionSkill
- summarize-changeSkill
- web-searchSkill
The file
Files
Implementation brake
on, the default without argument: do not create, modify or delete any project file. Reading, searching, building and testing stay open. Discuss with the user; when a change is needed, say which one and why. Only an explicit off from the user lifts this — not their approval of your proposal.
off: you may change code again. Implementation is likely what the user wants next, but raise any open point before starting.
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.