wct-adopt
Skill0 starsChanged 3 months agoMITView on GitHub
Adopt WCT (Write, Check, Trust) in an existing Python repository using strict-on-diff gates and measured whole-repository ratchets. Use for migration, template installation, initial baselining, provider adapter generation, or introducing hardening without requiring an immediate rewrite.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/wct.mdcCursor rule
- wct-acceptanceSkill
- wct-adoptSkill
- wct-architectureSkill
- wct-crapSkill
- wct-dependenciesSkill
- wct-doctorSkill
- wct-drySkill
- wct-gateSkill
- wct-hardeningSkill
- wct-mutateSkill
- wct-ratchetSkill
- wct-reviewSkill
- wct-securitySkill
- wct-test-honestySkill
- wct-acceptanceSkill
- wct-architectureSkill
- wct-crapSkill
- wct-dependenciesSkill
- wct-doctorSkill
- wct-drySkill
- wct-gateSkill
- wct-hardeningSkill
- wct-mutateSkill
- wct-ratchetSkill
- wct-reviewSkill
- wct-securitySkill
- wct-test-honestySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 12
Keep strict thresholds on changed code and ratchets on untouched legacy code.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Adopt WCT
- Inventory language, source roots, tests, framework boundaries, and existing CI.
- Copy the harness without overwriting project behavior.
- Configure architecture layers and forbidden externals in
governance/policy.yaml. - Measure existing metrics into baselines; do not invent favorable values.
- Keep strict thresholds on changed code and ratchets on untouched legacy code.
- Build provider rules, create the integrity lock, run doctor, then run commit tier.
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.