adversarial-reviewer

原文涵盖的主题

• Adversarial Code Reviewer
• Description
• Features
• Usage
• Examples
• Example: Reviewing a PR Before Merge
• Problem This Solves
• Table of Contents

Adversarial code review skill that forces genuine perspective shifts through three hostile reviewer personas (Saboteur, New Hire, Security Auditor). Each persona MUST find at least one issue — no "LGTM" escapes. Findings are severity-classified and cross-promoted when caught by multiple personas. Three adversarial personas — Saboteur (production breaks), New Hire (maintainability), Security Auditor (OWASP-informed) Mandatory findings — Each persona must surface at least one issue, eliminating rubber-stamp reviews Severity promotion — Issues caught by 2+ personas are promoted one severity level Self-review trap breaker — Concrete techniques to overcome shared mental model blind spots Structured verdicts — BLOCK / CONCERNS / CLEAN with clear merge guidance Produces a structured report with findings from all three personas, deduplicated and severity-ranked, ending with a BLOCK/CONCERNS/CLEAN verdict. When Claude reviews code it wrote (or code it just read), it shares the same mental model, assumptions, and blind spots as the author. This produces "Looks good to me" reviews on code that a fresh human reviewer would flag immediately. Users report this as one of the top frustrations with

这里只展示节选，请以完整原文和当前要求为准。