Adversarial Review Skill

Use this skill for an independent final challenge after implementation or a primary review is complete. Always load review-verification-protocol before reporting findings. For repository changes, also load code-review.

Do not use it to implement changes, debug an active unexplained failure, or replace the first focused review of a diff.

Workflow

1. Compare the request, acceptance criteria, diff, tests, documentation, and prior agent claims.
2. Re-run or independently inspect the strongest available evidence instead of accepting summaries at face value.
3. Challenge one plausible hidden failure mode, including invalid states, untested boundaries, scope creep, and regressions.
4. Report only findings supported by reproducible evidence. Distinguish blockers from follow-ups and explicitly clear disproved concerns.
5. Record skipped checks, assumptions, and residual risk before recommending a merge or handoff.

Output

Return a merge recommendation with verified evidence, blockers, follow-ups, skipped validation, and assumptions that still need proof.