Stats
Actions
Tags
From mutation-testing
Configures mewt/muton mutation testing campaigns by scoping targets, tuning timeouts, and optimizing runs for Rust, Go, TypeScript, and JavaScript codebases.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mutation-testing:mutation-testingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **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`.
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
mewtcommands, but they work exactly the same withmuton. File names change accordingly:mewt.toml→muton.toml,mewt.sqlite→muton.sqlite.
Use this skill when the user:
mewt run and needs help getting set up firstDo not use this skill when the user:
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.
| 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 |
# 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
npx claudepluginhub trailofbits/skills --plugin mutation-testingRuns mutation testing workflow: mutates source code module-by-module, executes tests per mutation, writes tests for survivors, verifies, commits. Tracks multi-session progress.
Runs mutation testing to validate test suite quality across multiple stacks (Stryker, Infection, go-mutesting, mutmut, Vitest). Use when verifying test effectiveness or after generating tests.
Performs mutation testing using Claude as the mutation engine: generates code mutants, runs tests, tracks kill/survive rates, identifies test gaps, and recommends test improvements. No external mutation tools required.