By name: next-mutation
description: Pick the next module to audit with base:mutation-testing and dispatch it. Walks ${CLAUDE_PLUGIN_DATA}/mutation-audits/<consumer-slug>/audits.json plus git as ground truth and ranks candidates by three signals — changed since last audit, dependency-affected (lockfile changed since the audit captured its fingerprint), and stale (audit older than N days). Reached as a sub-mode of /base:next via /base:next mutation [<hint>] [auto], or invoked directly as /base:next-mutation [<hint>] [auto]. Always auto-dispatches the top candidate without confirmation; detail mode renders top-3 rationale first, auto mode prints a single notice line.
user-invocable: true
argument-hint: "(no args = detail) | auto | [auto]"
allowed-tools: Read, Bash, Skill, Grep, Glob
context: fork
agent: next-mutation-walker
User Question
$ARGUMENTS
The canonical dispatch logic (Steps 0–6) lives in plugins/base/agents/next-mutation-walker.md.
The walker carries: audit-store read, signal computation (changed / dep-affected / stale), tier
ranking, hint short-circuit, never-audited fallback, and mode-gated dispatch. Invoke it with
the arguments above.