mutatelisted
Install: claude install-skill x-mesh/xm
# x-mutate
<Purpose>
Check whether the tests already in a repository detect bounded changes to the lines a branch or an x-build task changed. This skill is a thin interface over `xm mutate` and `xm build mutate`: external tools generate and run every mutant, and the xm engine owns the change set, the report, and the attention ledger.
</Purpose>
<Use_When>
- The user asks for mutation testing, surviving mutants, or whether the tests would catch a bug in changed code.
- The user invokes /xm:mutate, $xm:mutate, or $xm-mutate.
</Use_When>
<Do_Not_Use_When>
- The user wants tests written or generated. This skill only measures existing tests.
- Every changed file is in a language without an adapter. Only rust, javascript (JS/TS), go, and swift are supported.
</Do_Not_Use_When>
## Workflow
1. Read `$ARGUMENTS` as one of two forms. Never interpolate the raw `$ARGUMENTS` string into a shell command.
- Diff mode (the default), run as `xm mutate`: `--diff <base> [--lang <names>] [--timeout-ms N] [--json]`
- Task mode, run as `xm build mutate`: `<task-id> [--project NAME] [--base REF] [--lang <names>] [--timeout-ms N] [--json]`, with an optional leading `--task`
- The entries do not share flags. `xm mutate` takes `--diff` and refuses `--task`, `--list`, `--base` and `--project`; `xm build mutate` takes `--list`/`--task`/`--base` and refuses `--diff`.
2. With no arguments, use diff mode and ask only for the base with AskUserQuestion. Offer the branches that `git branch --lis