adversarial-review

Coordinates external LLM reviews of code, plans, and documents with per-finding verification and convergence circuit breakers.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill adversarial-review-ab300819
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/adversarial-review
Command: npx skills add https://github.com/ab300819/keel-workflow --skill adversarial-review-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Internal self-review tends to rubber-stamp its own work, and a single external review pass can produce false positives or truncated results that look like a clean pass. This Skill orchestrates an independent external LLM reviewer, verifies every finding against the actual code or documents, and loops until the review converges or a circuit breaker forces a decision. ## Core Features & Use Cases - External review orchestration: Dispatches review briefs to codex CLI, codex-mcp, or a fallback sub-agent with a four-tier degradation chain and explicit failure classification (quota exhaustion, truncation, protocol incompatibility). - Per-finding verification: Each external finding is independently confirmed, rejected with evidence, or marked partial, with severity ratings (P1/P2/P3) and concrete fix proposals. - Convergence tracking and circuit breakers: A weighted health score per round detects non-converging review loops, triggers trend warnings, and forces a retrospective with root-cause analysis after repeated stalls or a 5-round safety limit. - Use Case: After finishing a feature branch, run the skill to have an external model attack your uncommitted diff, then walk through each reported issue with evidence-based confirmation or rebuttal before merging. ## Quick Start Ask the AI to run an adversarial review on the current uncommitted changes and verify each finding before proposing fixes.

Frequently Asked Questions about adversarial-review

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

FAQPage Schema
How do I get an independent second opinion on my code changes?

Run the adversarial review on your uncommitted diff. It collects the workspace changes, sends them to an external LLM reviewer, then verifies each reported finding against the actual code before presenting confirmed issues with fix proposals.

How does adversarial code review differ from a normal code review?

Adversarial review instructs the external reviewer to actively break confidence in the change rather than validate it, targeting auth, data loss, race conditions, and rollback risks. Every finding is then independently verified with cited evidence before being accepted or rejected.

What happens when the external reviewer's quota runs out mid-review?

Quota exhaustion routes to an alternate billing backend (T1b) if one is configured, never silently downgrading to a weaker reviewer. If no alternate exists, the skill reports the exhausted channel and reset time, then stops for a user decision.

Can truncated review output be mistaken for a passing review?

No. Output missing the required verdict field or end marker is flagged as truncated and never consumed as findings. The skill reruns the review or switches channels instead of treating incomplete output as a clean pass.

When does the review loop stop automatically?

The loop stops when the health score converges, or a circuit breaker fires when the score fails to drop by round three or the five-round safety limit is hit. A forced retrospective then presents trend data, root-cause analysis, and options to continue, accept, or roll back.