mutmut-report
Skill0 starsChanged 6 days agoMITView on GitHub
Triages surviving mutmut mutants and reports the test fixes worth making. Use when the user asks which mutants survived. Not for running mutmut or coverage (coverage-gaps).
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- claude-arsenal/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- coverage-gapsSkill
- dep-upgradeSkill
- designSkill
- executionSkill
- explore-ideaSkill
- gate-checkSkill
- githubSkill
- initSkill
- litcriticSkill
- pin-checkSkill
- pypi-releaseSkill
- python-bootstrapSkill
- queue-addSkill
- queue-nextSkill
- queue-statusSkill
- reviewSkill
- session-endSkill
- shipSkill
- specifySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Run it from the directory where mutmut run was executed (cd there first if it is another checkout), since it reads mutants/ from the …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
mutmut Survivors Report
Runs the analysis script against a project's existing mutants/ workspace and
reports which surviving mutants are real test gaps and which are safe to accept.
CANARY: mutmut-report-loaded-2026-06-02-87a56d2e-e3c5c50abfce45f3
Step 1 — Run the script
Run it from the directory where mutmut run was executed (cd there first if
it is another checkout), since it reads mutants/ from the current directory.
$ARGUMENTS is forwarded verbatim — --module validate, --max 20,
--venv .venv.
python3 "${CLAUDE_SKILL_DIR}/scripts/analyze_mutmut.py" $ARGUMENTSStep 2 — Report
- Modules with real gaps, and how many.
- For each real gap, the fix: a tighter assertion or a missing case.
- Equivalent and untestable mutants, confirmed as accepted in one line.
- The top 2–3 fixes to make next.
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.

