メニュー
Alias for improve-test-leverage biased to ADD moves that raise the suite's promotion-ladder stage — ruleset registrations, composed-optic laws, negative fixtures, properties replacing examples. Use to raise mutant-kill capacity per test line.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orchestrates a coverage + mutation improvement cycle tuned to cats-eo's algebraic structure. Reads scoverage + stryker4s reports, triages surviving mutants, and drives every test artifact UP the promotion ladder (examples → property → law) so the suite kills more mutants with FEWER test lines. Phases live in phases/*.md, each with its own model assignment. Mandatory consolidation and law-scan phases close every run; law promotion is user-gated. Supports a measured eval-optimization loop ("loop" argument).
Alias for improve-test-leverage biased to killing currently-surviving mutants and covering uncovered branches — the gap-closing mode. Use when the QA page shows survivors or NoCoverage clusters that should be dead.
Alias for improve-test-leverage running ONLY the consolidation pipeline — shrink test count and LOC while holding every kill. Replaces example clusters with properties, deletes tests that restate laws, merges redundant properties.
Use cats-eo (existential optics for Scala 3) to specify pinpointed read/write operations on nested case classes, JSON byte buffers, Avro records, or circe ASTs. One Optic[S, T, A, B, F] trait, several carriers, uniform .get/.modify/.replace/.foldMap/.andThen surface.
| name | test-upgrade |
| description | Alias for improve-test-leverage biased to ADD moves that raise the suite's promotion-ladder stage — ruleset registrations, composed-optic laws, negative fixtures, properties replacing examples. Use to raise mutant-kill capacity per test line. |
| model | sonnet |
Alias for improve-test-leverage. Run phases 1-5 of
.claude/skills/improve-test-leverage/ (reports → triage → plan → execute →
eval) with this bias: ADD moves only, highest ladder stage first; no
CONSOLIDATE planning (that is /test-prune's job); CLASSIFY-OUT allowed.
Plan rows must still answer phase 3's reduction question — subsumed examples
are listed for deletion even in upgrade mode.
Arguments pass through (e.g. loop 3, a module focus).
Announce as: "Using improve-test-leverage (test-upgrade alias)."
