Code Review

Code Review

Standalone adversarial code review of any diff or PR — and it sharpens developer-workflows' /review when both are installed. The framing is "assume the code has bugs": a reviewer returns a failing test, a DEFECT: file:line, or NO ISSUES FOUND — never prose.

Full primitive detail: code-review design.

How it composes

• Standalone — review any diff or PR directly; requires: [].
• Enhances developer-workflows — at /review the phase dispatches the adversarial reviewers; evidence-tracker guards /work's checkbox-flips. Both engage only when developer-workflows is also installed.
• Hosts — command + both reviewer agents are host-symmetric; the cross-model reviewer degrades gracefully without gemini; the evidence-tracker PreToolUse hook is Claude-only (Antigravity limitations).

Why it works

A reviewer primed to assume bugs finds real ones; demanding a failing test or a file:line defect keeps the output actionable. The cross-model pass escapes the same-model echo chamber. See Why adversarial review.

Related

• First code review — the tutorial.
• Review a change · Simplify a diff · In-flight decision review — the how-tos.
• Why adversarial review — why the assume-bugs framing works.
• Developer Plugin Suite design — the developer-workflows / safety / code-review split.

Architecture · Plugins · Home