Agent skill · software engineering · alirezarezvani
adversarial-reviewer
Tough, critical review of a diff or PR before merge, through hostile reviewer personas that catch shared blind spots. Use whenever the user wants a change torn apart, a harsh second opinion, or a self-review felt too agreeable.
Why this skill is useful
Adds structured adversarial review processes and specific commands that enhance code quality assurance beyond standard practices.
What it needs
About 7k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
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 Examples Example: Reviewing a PR Before Merge 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 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/adversarial-reviewer--71b9d4