How do I install the Mutation Testing skill?

Run npx skillmds@latest add kunanonj/mutation-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mutation Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mutation Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mutation Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mutation Testing?

KunanonJ (@kunanonj) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mutation Testing by kunanonj — Agent Skill

Name: Mutation Testing
Author: KunanonJ

Mutation Testing

Configures mewt or muton mutation testing campaigns — scopes targets, tunes timeouts, and optimizes long-running runs. Use when the user mentions mewt, muton, mutation testing, or wants to configure or optimize a mutation testing campaign.

KunanonJ 7e55a3d 5 files · 24.3 KB Updated Sep 17, 2026

File contents

Mutation Testing — Campaign Configuration (mewt/muton)

Note: muton and mewt share identical interfaces but target different languages — mewt for general-purpose languages (Rust, Solidity, Go, TypeScript, JavaScript), muton for TON smart contracts (Tact, Tolk, FunC). All examples use mewt commands, but they work exactly the same with muton. File names change accordingly: mewt.toml → muton.toml, mewt.sqlite → muton.sqlite.

When to Use

Use this skill when the user:

Mentions "mewt", "muton", or "mutation testing"
Needs to configure or optimize a mutation testing campaign
Wants to run mewt run and needs help getting set up first

When NOT to Use

Do not use this skill when the user:

Wants to analyze or report on completed campaign results
Asks about tests or coverage without mentioning mutation testing

Quick Start

Load workflows/configuration.md — a 5-phase guide from mewt init to a validated, ready-to-run campaign.

General question or unfamiliar command? Run mewt --help or mewt <subcommand> --help, then assist.

Reference Index

File	Content
workflows/configuration.md	5-phase guide: init, scope, optimize, validate, run
references/optimization-strategies.md	Per-file targeting, two-phase campaigns, mutation type filtering

Essential Commands

# Initialize and mutate
mewt init                    # Create mewt.toml and mewt.sqlite
mewt mutate [paths]          # Generate mutants without running tests
mewt run [paths]             # Run the full campaign

# Inspect configuration and scope
mewt print config            # View effective configuration
mewt print targets           # Table of all targeted files
mewt print mutations --language [lang]  # Available mutation types
mewt status                  # Mutant count and per-file breakdown

# Investigate specific mutants
mewt print mutants --target [path]   # All mutants for a file
mewt print mutants --severity high   # Filter by severity
mewt print mutant --id [id]          # View mutated code diff
mewt test --ids [ids]                # Re-test specific mutants

What Results Mean

Caught/TestFail: Tests detected the mutation (good)
Uncaught: Mutation survived — indicates untested logic
Timeout: Tests took too long, inconclusive
Skipped: A more severe mutant already failed on the same line

---name: mutation-testingdescription: Configures mewt or muton mutation testing campaigns — scopes targets, tunes timeouts, and optimizes long-running runs. Use when the user mentions mewt, muton, mutation testing, or wants to configure or optimize a mutation testing campaign.---# Mutation Testing — Campaign Configuration (mewt/muton)> **Note**: muton and mewt share identical interfaces but target different languages — mewt for general-purpose languages (Rust, Solidity, Go, TypeScript, JavaScript), muton for TON smart contracts (Tact, Tolk, FunC). All examples use `mewt` commands, but they work exactly the same with `muton`. File names change accordingly: `mewt.toml` → `muton.toml`, `mewt.sqlite` → `muton.sqlite`.## When to UseUse this skill when the user:- Mentions "mewt", "muton", or "mutation testing"- Needs to configure or optimize a mutation testing campaign- Wants to run `mewt run` and needs help getting set up first## When NOT to UseDo not use this skill when the user:- Wants to analyze or report on completed campaign results- Asks about tests or coverage without mentioning mutation testing---## Quick StartLoad [workflows/configuration.md](workflows/configuration.md) — a 5-phase guide from `mewt init` to a validated, ready-to-run campaign.**General question or unfamiliar command?**Run `mewt --help` or `mewt <subcommand> --help`, then assist.---## Reference Index| File | Content ||------|---------|| [workflows/configuration.md](workflows/configuration.md) | 5-phase guide: init, scope, optimize, validate, run || [references/optimization-strategies.md](references/optimization-strategies.md) | Per-file targeting, two-phase campaigns, mutation type filtering |---## Essential Commands```bash# Initialize and mutatemewt init # Create mewt.toml and mewt.sqlitemewt mutate [paths] # Generate mutants without running testsmewt run [paths] # Run the full campaign# Inspect configuration and scopemewt print config # View effective configurationmewt print targets # Table of all targeted filesmewt print mutations --language [lang] # Available mutation typesmewt status # Mutant count and per-file breakdown# Investigate specific mutantsmewt print mutants --target [path] # All mutants for a filemewt print mutants --severity high # Filter by severitymewt print mutant --id [id] # View mutated code diffmewt test --ids [ids] # Re-test specific mutants```---## What Results Mean- **Caught/TestFail**: Tests detected the mutation (good)- **Uncaught**: Mutation survived — indicates untested logic- **Timeout**: Tests took too long, inconclusive- **Skipped**: A more severe mutant already failed on the same line

Frequently asked questions