adversarial-review-cycle

What problem does it solve?

It prevents avoidable production failures by forcing an explicitly hostile, adversarial review loop that hunts for bugs, security gaps, and edge cases the implementer is likely to miss.

Core Features & Use Cases

• Two-pass adversarial hardening: Run a Round 1 broad attack and then a Round 2 review from a different angle (e.g., security, correctness, UX, or performance) before considering the work ready.
• Full-diff, test-inclusive scrutiny: Require the reviewer to read the full git diff (or read each changed file end-to-end) and to read the tests themselves, not rely on summaries.
• Severity-based triage and gating: Classify findings as P0/P1/P2/P3, fix P0/P1 before proceeding, and only declare “ship clean” when both rounds return acceptably clean results (with explicit rationale for accepted lower-severity issues).

Quick Start

Run an adversarial review cycle on your completed changes by asking for a “hardening pass” in explicitly hostile terms like “Poke holes in this and try to break it before I ship.”