mutation-check
Skill808 starsChanged 8 days agoApache-2.0View on GitHub
Run cargo-mutants for changed coop logic and keep .cargo/mutants.toml synchronized. Use when logic-dense modules change, before refactors, or when asked to verify mutation coverage.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- scoobydont-666/shared-claude-skillstheir own version, first seen Nov 1, 2026
- ArthurC02/SkillHubtheir own version, first seen Oct 31, 2026
- hidevinliu/red-green-modetheir own version, first seen Aug 1, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- jisuzzzz/haechi★ 17same name
- hidevinliu/red-green-mode★ 11same name
- ArthurC02/SkillHub★ 1same name
- scoobydont-666/shared-claude-skills★ 1same name
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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- babysit-my-prsSkill
- babysit-prSkill
- closeout-reviewSkill
- implement-to-draft-prSkill
- integrationSkill
- reviewSkill
- closeout-reviewSkill
- mutation-checkSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Run a full-file sweep for each touched scoped module and library tests only: cargo mutants -f src/<file>.rs -- --lib.
- Very specific: line 25
Do not spend a full mutation run on whole-module exclusions (backend.rs, lima.rs, setup.rs, update.rs, ssh.rs, vm.rs, network.rs, …
“Common” is measured: kept by at least 6 in 10 of the 3 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
Mutation Check
Read docs/testing.md first.
- Inspect the diff before running. New functions in logic modules that shell
out, drive
&PlatformBackend, read a TTY, or write stdout must be excluded in.cargo/mutants.tomlin the same PR. Extract and test their pure decision logic. Pure helpers remain in scope. - Sanity-check changed exclusions with
cargo mutants --list -f <file>. - Run a full-file sweep for each touched scoped module and library tests only:
cargo mutants -f src/<file>.rs -- --lib. Redirect output to a file; do not pipe a long run throughheadorgrep. - Triage
mutants.out/missed.txt: add a discriminating test for real gaps, mark genuinely equivalent mutants with a narrow documented skip, and delete dead code. Confirm each new test by re-running the mutant or deliberately breaking the protected behavior. - Report files swept, missed count before/after, every survivor's disposition,
and whether
.cargo/mutants.tomlchanged.
Do not spend a full mutation run on whole-module exclusions (backend.rs,
lima.rs, setup.rs, update.rs, ssh.rs, vm.rs, network.rs,
port_forward.rs, cmd.rs, prompt.rs, main.rs). Instead, identify the
unit/integration blind spot explicitly and test extracted pure logic directly.
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.