Configures PIT (PITest) for mutation testing of JVM projects (Java, Kotlin via the Kotlin plugin) - wires the `pitest-maven` or `pitest-gradle-plugin` with `mutationThreshold`, `coverageThreshold`, target classes/tests filtering, runs `mvn pitest:mutationCoverage`, parses the HTML + XML reports. Use when the JVM suite needs mutation-quality verification - the canonical Java mutation testing tool, fast (PIT analyzes "in minutes rather than days").
75
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Detailed pitfalls and constraints for pitest-mutation. Linked inline from that skill's SKILL.md.
| Anti-pattern | Why it fails | Fix |
|---|---|---|
| Mutating the entire codebase every PR | Slow; team disables. | withHistory + per-changed-file scope. |
mutationThreshold: 100 | Unreachable; first failed run blocks all PRs. | Start at the current baseline; ratchet up. |
| Mixed Maven/Gradle config (both plugins active) | Conflicting configurations; cryptic errors. | Pick one build tool. |
| Missing JUnit 5 plugin dependency | Tests don't run; mutation coverage 0. | Add pitest-junit5-plugin for JUnit 5. |
Targeting test classes in targetClasses | Mutates test code; meaningless. | targetClasses = production package; targetTests = test package. |
All mutators (ALL mutator set) | Many irrelevant mutants; long runtime. | DEFAULTS (default) or STRONGER. |
targetClasses patterns.