do-adversarial-review

Hunt correctness bugs and regressions in a code diff using adversarial review.

2|Updated May 25, 2026
One-click install
npx skills add https://github.com/edheltzel/Do-Skills --skill do-adversarial-review-edheltzel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-adversarial-review
Source: https://github.com/edheltzel/Do-Skills/tree/main/skills/core/do-adversarial-review
Command: npx skills add https://github.com/edheltzel/Do-Skills --skill do-adversarial-review-edheltzel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often produce vague, low-signal feedback or miss regressions hiding in callers outside the diff. This Skill forces a distrust-first review of a change set, hunting only correctness bugs that can be triggered by a concrete input. ## Core Features & Use Cases - Diff-scoped bug hunting: Reviews only added and changed lines from git diff, then traces the blast radius into callers affected by changed signatures, nullability, or return shapes. - Structured bug taxonomy: Hunts twelve bug classes including null dereferences, off-by-one errors, swallowed errors, races, async mistakes, resource leaks, and partial refactors. - Trigger-gated reporting: Every finding must name the concrete input that triggers it, include severity and confidence, and survive a self-verification pass that tries to disprove it. - Use Case: Before merging a refactor, ask for an adversarial review of the diff to catch a newly-nullable return value that breaks a stale caller the diff never shows. ## Quick Start Ask the AI to adversarially review the current git diff and report only correctness bugs it can trigger with a concrete input.

Frequently Asked Questions about do-adversarial-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find bugs in a code diff before merging?▼

Run an adversarial review on the git diff that assumes the change is wrong until a concrete input proves otherwise. Each finding must name the triggering input, include severity and confidence, and survive a self-verification pass before being reported.

What kinds of bugs does adversarial code review catch?▼

It targets twelve correctness bug classes: null dereferences, off-by-one errors, swallowed errors, happy-path gaps, races, state mutation, async mistakes, type coercion, resource leaks, inverted logic, contract mismatches, and partial refactors.

Does adversarial review only look at the changed lines?▼

Findings must tie to changed lines, but the review also traces the blast radius into callers. A rename or newly-nullable return breaks stale callers that a pure diff review structurally misses.

Can adversarial review apply fixes to the code it finds?▼

No, the review is strictly read-only. It proposes suggested fixes for each finding but never applies them or touches code outside the change set.

When should I use adversarial review instead of a security review?▼

Use it for correctness bugs and regressions in a change set, not vulnerabilities. Security concerns are explicitly handed off to a separate security-review skill, and style issues go to other review lenses.