wct-mutate
Skill0 starsChanged 3 months agoMITView on GitHub
Run WCT differential mutation analysis and eliminate surviving mutants. Use after behavior changes, when coverage looks suspiciously easy, for G-MUT or G-MUT-SITES failures, and before hardening handoff.
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-adoptSkill
- wct-architectureSkill
- wct-crapSkill
- wct-dependenciesSkill
- wct-doctorSkill
- wct-drySkill
- wct-gateSkill
- wct-hardeningSkill
- wct-ratchetSkill
- wct-reviewSkill
- wct-securitySkill
- wct-test-honestySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run uv run wct mutate scan.
- Very specific: line 9
Run uv run wct mutate run.
- Very specific: line 12
Only after green, run uv run wct mutate update-manifest and include the manifest with the verified change.
≈ “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
Harden with mutation
- Run
uv run wct mutate scan; split any changed file above 100 mutation sites for behavioral reasons. - Run
uv run wct mutate run; the manifest selects changed functions. - For uncovered mutants, add a test that reaches the behavior. For survivors, strengthen assertions or simplify equivalent code.
- Require zero survivors in changed code.
- Only after green, run
uv run wct mutate update-manifestand include the manifest with the verified change.
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.