Individual skill
mutation-testing-advisor
Analyzes test suites to identify surviving mutants, weak assertions, and false confidence in line coverage.
skills/testing/mutation-testing-advisor/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 582 bytesSKILL.mdcore · 1,631 bytesexamples/example.mddoc · 911 bytes
Read excerpt
## Purpose
Evaluate the true fault-detection capability of a test suite by simulating code mutations (inverting conditionals, altering arithmetic, removing function calls) and highlighting tests that pass despite broken logic.
## When to Use
- A codebase has 90%+ line coverage but bugs still regularly slip into production.
- Reviewing unit tests that assert on execution without verifying state changes.
- Setting up Stryker or Mutmut mutation testing in critical packages.
## What to Analyze
1. **Mutant Categories**:
- Conditional Boundary Mutations (`>` swapped for `>=`).