What problem does it solve? Single-reviewer code reviews tend to rubber-stamp changes, letting security holes, unmet acceptance criteria, and fake placeholder returns slip into merged branches. ## Core Features & Use Cases - Parallel adversarial fan-out: Spawns three independent subagents in one message, each with a distinct rubric covering security/correctness, code quality, and runtime reproduction. - Evidence-gated verdicts: Requires web_verify screenshots for front-end changes, flow_audit evidence for cross-surface changes, and impact_audit coverage for shared-contract changes before passing. - Deduped synthesis: Merges findings by file:line and normalized claim, counts reviewer votes, and emits a machine-readable verdict of pass, fix-required, or block. - Use Case: Before merging a pull request that touches both a React component and its API endpoint, run this review to confirm the acceptance criteria actually reproduce end-to-end and that no injection or broken caller exists in the diff. ## Quick Start Ask the assistant to run a thermo-nuclear adversarial review on the current branch diff against the base branch before merging.