What problem does it solve? Mutation testing campaigns can take many hours when targets, timeouts, and mutation types are misconfigured. This Skill guides you through setting up mewt or muton so campaigns run with the right scope, realistic duration estimates, and optimized settings before you commit to a long-running run. ## Core Features & Use Cases - Campaign Configuration: Walks through a 5-phase workflow from mewt init to a validated, ready-to-run campaign, covering target patterns, mutant generation, and final validation. - Duration Estimation & Optimization: Calculates worst-case campaign time (mutant count × test duration) and applies strategies like per-file targeting, severity filtering, and two-phase campaigns when estimates exceed acceptable limits. - Timeout Tuning: Handles recompilation-heavy languages like Solidity/Foundry by measuring warm-cache versus cold-cache test times and setting manual timeouts when needed. - Use Case: You have a Rust project where mewt run would take an estimated 20 hours. Use this Skill to narrow targets to critical components, restrict mutation types to high/medium severity, and reduce the campaign to a few hours. ## Quick Start Ask the assistant to configure a mewt mutation testing campaign for your project and optimize it if the estimated runtime is too long.
