bug-huntAdversarial post-change review. Spawn three parallel Task agents focused on distinct bug categories — race / concurrency, edge-case / null-empty, and error-swallow / silent-failure — to surface defects that linear self-review systematically misses. The siblings of magi (pre-flight) and code-review (
dual-magi-reviewIndependent multi-perspective peer review for large design docs. Spawn 3 same-family sub-agent reviewers AND a cross-family reviewer (= different model family、 default: codex-exec) to cancel shared training-data bias. Cross-family is **default mandatory** since v0.6.0 (= gh #195 incident: 4 Claude s
magi-battleRed-vs-blue adversarial team battle over a design that has already reached dual-magi PLATEAU. Red team builds the strongest attacks (chaining the DEFERRED / low-severity findings review filed away one-by-one), blue team defends from the design + rationale, a cross-family blinded judge scores who won
magiContract mirror for the three-perspective preflight review used before high-stakes changes. This Claude surface is an explicit fail-closed availability boundary until a Claude-native structural runner ships; it must not claim deterministic reviewer independence from prose alone. USE WHEN any one tri
ultramagiEnd-to-end rigor loop for a non-trivial, hard-to-reverse change: local plan/design → reversibility-classified briefing → bounded code/measurement → dual-magi/bug-hunt before each irreversible boundary → code-review → next. A superset of dual-magi-review that drives the WHOLE lifecycle, not just one