mutation-testing

Run diff-scoped mutation testing on changed code across multiple languages.

23|7|Updated Sep 8, 2025
One-click install
npx skills add https://github.com/pvillega/claude-templates --skill mutation-testing-pvillega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mutation-testing
Source: https://github.com/pvillega/claude-templates/tree/main/plugins/ct/skills/mutation-testing
Command: npx skills add https://github.com/pvillega/claude-templates --skill mutation-testing-pvillega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-scoped mutation testing to verify that your tests catch real bugs by introducing small code changes (mutations) and checking if the test suite detects them.

Always diff-scoped. Full-project mutation testing is impractical interactively. This skill scopes to changed code by default.

Core Features & Use Cases

  • Language detection & tool selection
  • Phase-based mutation workflow across multiple languages
  • Diff-scoped mutation targets and actionable results

Quick Start

Run mutation testing on the changed code to verify test quality and reveal gaps.

Frequently Asked Questions about mutation-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is diff-scoped mutation testing and why use it?

Diff-scoped mutation testing verifies that your tests catch real bugs by introducing small code changes (mutations) only into changed code and checking if the test suite detects them, avoiding the impracticality of full-project mutation testing interactively.

How does mutation testing detect the right tool for my programming language?

Mutation testing detects the programming language of your project and automatically selects a suitable tool per language, such as Stryker, mutmut, cargo-mutants, PIT, or gremlins, to run mutations on the changed code.

How do I run mutation testing only on my changed code?

You can run mutation testing on changed code by using a diff-scoped targeting workflow that automatically limits mutations to the diff, runs the selected tool, and reports mutation outcomes for triage.

Does mutation testing work with Stryker, cargo-mutants, and PIT?

Yes, mutation testing supports multiple languages by selecting the appropriate tool per language, including Stryker, cargo-mutants, PIT, gremlins, and mutmut, to ensure diff-scoped targeting and actionable results.

Why should I scope mutation testing to changed code instead of the full project?

Full-project mutation testing is impractical interactively, so scoping to changed code ensures faster, actionable results by verifying test quality and revealing gaps only in the modified parts of the codebase.