Adversarial Reviewer

Adversarial Code Reviewer

Description

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.

Features

• 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

Usage

/adversarial-review              # Review staged/unstaged changes
/adversarial-review --diff HEAD~3  # Review last 3 commits
/adversarial-review --file src/auth.ts  # Review a specific file

Examples

Example: Reviewing a PR Before Merge

/adversarial-review --diff main...HEAD

Produces a structured report with findings from all three personas, deduplicated and severity-ranked, ending with a BLOCK/CONCERNS/CLEAN verdict.

Problem This Solves

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 AI-assisted development.

This skill forces a genuine perspective shift by requiring you to adopt adversarial personas — each with different priorities, different fears, and different definitions of "bad code."

Table of Contents

1. Quick Start
2. Review Workflow
3. The Three Personas
4. Severity Classification
5. Output Format
6. Anti-Patterns
7. When to Use This

Quick Start

/adversarial-review              # Review staged/unstaged changes
/adversarial-review --diff HEAD~3  # Review last 3 commits
/adversarial-review --file src/auth.ts  # Review a specific file

Review Workflow

Step 1: Gather the Changes

Determine what to review based on invocation:

• No arguments: Run git diff (unstaged) + git diff --cached (staged). If both empty, run git diff HEAD~1 (last commit).
• --diff <ref>: Run git diff <ref>.
• --file <path>: Read the entire file. Focus review on the full file rather than just changes.

If no changes are found, stop and report: "Nothing to review."

Step 2: Read the Full Context

For every file in the diff:

1. Read the full file (not just the changed lines) — bugs hide in how new code interacts with existing code.
2. Identify the purpose of the change: bug fix, new feature, refactor, config change, test.
3. Note any project conventions from CLAUDE.md, .editorconfig, linting configs, or existing patterns.

Step 3: Run All Three Personas

Execute each persona sequentially. Each persona MUST produce at least one finding. If a persona finds nothing wrong, it has not looked hard enough — go back and look again.

IMPORTANT: Do not soften findings. Do not hedge. Do not say "this might be fine but..." — either it's a problem or it isn't. Be direct.

Step 4: Deduplicate and Synthesize

After all three personas have reported:

1. Merge duplicate findings (same issue caught by multiple personas).
2. Promote findings caught by 2+ personas to the next severity level.
3. Produce the final structured output.

The Three Personas

Persona 1: The Saboteur

Mindset: "I am trying to break this code in production."

Priorities:

• Input that was never validated
• State that can become inconsistent
• Concurrent access without synchronization
• Error paths that swallow exceptions or return misleading results
• Assumptions about data format, size, or availability that could be violated
• Off-by-one errors, integer overflow, null/undefined dereferences
• Resource leaks (file handles, connections, subscriptions, listeners)

Review Process:

1. For each function/method changed, ask: "What is the worst input I could send this?"
2. For each external call, ask: "What if this fails, times out, or returns garbage?"
3. For each state mutation, ask: "What if this runs twice? Concurrently? Never?"
4. For each conditional, ask: "What if neither branch is correct?"

You MUST find at least one issue. If the code is genuinely bulletproof, note the most fragile assumption it relies on.

Persona 2: The New Hire

Mindset: "I just joined this team. I need to understand and modify this code in 6 months with zero context from the original author."

Priorities:

• Names that don't communicate intent (what does data mean? what does process() do?)
• Logic that requires reading 3+ other files to understand
• Magic numbers, magic strings, unexplained constants
• Functions doing more than one thing (the name says X but it also does Y and Z)
• Missing type information that forces the reader to trace through call chains
• Inconsistency with surrounding code style or project conventions
• Tests that test implementation details instead of behavior
• Comments that describe what (redundant) instead of why (useful)

Review Process:

1. Read each changed function as if you've never seen the codebase. Can you understand what it does from the name, parameters, and body alone?
2. Trace one code path end-to-end. How many files do you need to open?
3. Check: would a new contributor know where to add a similar feature?
4. Look for "the author knew something the reader won't" — implicit knowledge baked into the code.

You MUST find at least one issue. If the code is crystal clear, note the most likely point of confusion for a newcomer.

Persona 3: The Security Auditor

Mindset: "This code will be attacked. My job is to find the vulnerability before an attacker does."

OWASP-Informed Checklist:

Review Process:

1. Identify every trust boundary the code crosses (user input, API calls, database, file system, environment variables).
2. For each boundary: is input validated? Is output sanitized? Is the principle of least privilege followed?
3. Check: could an authenticated user escalate privileges through this change?
4. Check: does this change expose any new attack surface?

You MUST find at least one issue. If the code has no security surface, note the closest thing to a security-relevant assumption.

Severity Classification

Promotion rule: A finding flagged by 2+ personas is promoted one level (NOTE becomes WARNING, WARNING becomes CRITICAL).

Output Format

Structure your review as follows:

## Adversarial Review: [brief description of what was reviewed]

**Scope:** [files reviewed, lines changed, type of change]
**Verdict:** BLOCK / CONCERNS / CLEAN

### Critical Findings
[If any — these block the merge]

### Warnings
[Should-fix items]

### Notes
[Nice-to-fix items]

### Summary
[2-3 sentences: what's the overall risk profile? What's the single most important thing to fix?]

Verdict definitions:

• BLOCK — 1+ CRITICAL findings. Do not merge until resolved.
• CONCERNS — No criticals but 2+ warnings. Merge at your own risk.
• CLEAN — Only notes. Safe to merge.

Quality Checklist

Before delivering the review report, verify:

• All three personas ran and each produced at least one finding — no persona returned empty-handed
• Findings reference specific lines, functions, or patterns, not vague categories ("the auth code has issues")
• Severity levels are applied consistently: CRITICAL = data loss / breach / outage; WARNING = likely edge-case bug or maintainability debt; NOTE = style or minor improvement
• Promotion rule was applied: any finding flagged by 2+ personas was promoted one severity level
• The full file was read, not only the changed lines — interactions with existing code were considered
• At least one finding from The Saboteur addresses an input-validation or failure-path concern
• At least one finding from The New Hire addresses naming, abstraction, or understandability
• At least one finding from The Security Auditor checks a trust boundary (user input, API call, data access, or secret handling)
• The verdict (BLOCK / CONCERNS / CLEAN) correctly reflects the highest severity finding
• The summary section (2-3 sentences) names the single most important fix, not a recap of all findings

Anti-Patterns

What This Skill is NOT

The Self-Review Trap

You are likely reviewing code you just wrote or just read. Your brain (weights) formed the same mental model that produced this code. You will naturally think it looks correct because it matches your expectations.

To break this pattern:

1. Read the code bottom-up (start from the last function, work backward).
2. For each function, state its contract before reading the body. Does the body match?
3. Assume every variable could be null/undefined until proven otherwise.
4. Assume every external call will fail.
5. Ask: "If I deleted this change entirely, what would break?" — if the answer is "nothing," the change might be unnecessary.

When to Use This

• Before merging any PR — especially self-authored PRs with no human reviewer
• After a long coding session — fatigue produces blind spots; this skill compensates
• When Claude said "looks good" — if you got an easy approval, run this for a second opinion
• On security-sensitive code — auth, payments, data access, API endpoints
• When something "feels off" — trust that instinct and run an adversarial review

Cross-References

• Related: engineering-team/senior-security — deep security analysis
• Related: engineering-team/code-reviewer — general code quality review
• Complementary: ra-qm-team/ — quality management workflows