← ClaudeAtlas

mutation-testlisted

Mutation testing with two engines. Uses the project's NATIVE mutation runner (StrykerJS / Infection / mutmut / PIT / cargo-mutants) when one is configured — installing it on explicit consent when it is not — for a reproducible, comparable score; and an LLM-guided engine for the mutation classes native mutators cannot express: error-path removal, state mutation, async hazards, and security guard removal. Generates mutations, executes them against the relevant tests, and FIXES the tests whose gaps let a mutation survive — surviving mutants are closed in-run, not handed to another skill. Emits the cross-tool stryker-mutator.io/report.schema.json report alongside its own artifact. Flags: [path] (scope), full, --max N, --category, --runner auto|native|llm|hybrid, --break N, --no-install, --dry-run, --quick, --report-only.
greglas75/zuvo · ★ 6 · Code & Development · score 78
Install: claude install-skill greglas75/zuvo
# zuvo:mutation-test -- LLM-Guided Mutation Testing Intelligent mutation testing that targets meaningful behavioral gaps rather than random code changes. For each production file, the LLM generates mutations in 7 categories (boundary, logic, null, error, state, async, security), runs only the tests that cover that file, and closes the gaps it finds: every survivor is triaged as a real gap or an equivalent mutant, and each real gap gets the missing assertion added and re-probed in the same run. **Scope:** Production files that have associated test files. Measures how well existing tests detect real behavioral changes. **When to use:** After writing tests, before releases, when mutation score is unknown, when test suite feels shallow despite high line coverage. **Out of scope:** Writing a test suite from scratch (use `zuvo:write-tests`), fixing systematic test anti-patterns across many files (use `zuvo:fix-tests`), auditing test quality without execution (use `zuvo:test-audit`), code quality review (use `zuvo:review`). Adding the single missing assertion that a surviving mutant exposes is IN scope — that is the point of finding it. ## Argument Parsing Parse `$ARGUMENTS` as: `[path | full | continue] [--max N] [--category CATEGORY] [--runner MODE] [--break N] [--no-install] [--dry-run] [--quick] [--report-only]` | Flag | Env equivalent | Effect | |------|----------------|--------| | `[path]` | — | Scope to a specific directory or file | | `continue` | — | Resume an interrup