mutation testing
- Repo stars 0
- Author updated Aug 24, 2026, 11:09 PM
- Author repo skills
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @trailofbits · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# 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
# 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](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 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
Sections and files
Listed in source order.
sections -> When to Use → When NOT to Use → Quick Start → Reference Index → Essential Commands → What Results Mean
terms -> Note · General question or unfamiliar command? · Caught/TestFail · Uncaught · Timeout · Skipped
files/cmd -> mewt · muton · mewt.toml · muton.toml · mewt.sqlite · muton.sqlite · mewt run · mewt init
body sha256 -> 6b1e852634de
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 runand needs help getting set up firstWhen 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 initto a validated, ready-to-run campaign. General question or unfamiliar command? Runmewt --helpormewt <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
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