adversarial-review-loop

Runs adversarial subagent rounds that refute a code diff before pushing or opening a PR.

16|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SocialGouv/iterion --skill adversarial-review-loop-socialgouv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adversarial-review-loop
Source: https://github.com/SocialGouv/iterion/tree/main/skills/adversarial-review-loop
Command: npx skills add https://github.com/SocialGouv/iterion --skill adversarial-review-loop-socialgouv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often reach reviewers with defects that a hostile reading would have caught, and each external review gate cycle costs queue time and shared reviewer capacity. This Skill runs a self-review loop whose subagents try to break your diff rather than bless it, so findings die locally before anyone else reviews the change. ## Core Features & Use Cases - Adversarial rounds with budgets: Scope the change with git, announce a round estimate and ceiling from the changed-file count, and launch parallel subagents prompted to refute the code with executed proof. - Verified findings and fixes: Every finding and proposed fix is executed before being applied, fixes are applied at the class level rather than the site, and tests are mutation-proved by reintroducing the defect and requiring red. - Non-convergence exits and journaling: Detects loops auditing their own output, offers three named exits, and records every round in a JSONL journal with commit trailers like Adversarial-Rounds for auditability. - Use Case: Before pushing a feature branch, run adversarial rounds on the diff against origin/main, fix confirmed critical and high findings, then push and let the review gate's verdict close the loop. ## Quick Start Run one adversarial review round on my current uncommitted changes against origin/main and report any critical or high findings with executed proof.

Frequently Asked Questions about adversarial-review-loop

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

FAQPage Schema
How do I review my own code adversarially before opening a PR?▼

Scope the diff against the fetched merge base with origin/main, announce a round budget from the changed-file count, then launch subagents instructed to break the change with executed proof. Verify each finding and proposed fix before applying anything.

How many adversarial review rounds does a code change need?▼

Estimate from the changed-file count: roughly 3 rounds for up to 8 files, 6 for 9-25 files, and 8 for larger diffs, with ceilings of 5, 20, and 50 local rounds. The findings decide the next round, not the counter; measured convergence ranged from 1 to 8 rounds.

Why does git diff miss files when scoping a review?▼

git diff never lists untracked files, and the three-dot form compares commits so uncommitted changes are invisible. Combine a two-dot diff from the merge base with git ls-files --others run at the repository root, chained with && so an empty base cannot produce a plausible count.

When should I stop an adversarial review loop?▼

Stop only when no unassumed high or critical finding remains, and where a review gate exists its verdict closes the loop, not a sterile local round. Two consecutive rounds whose highs land on your own previous fixes signal non-convergence, requiring requalifying scope, changing approach, or testing the guarantee.

What are the limitations of adversarial subagent code review?▼

Proposed fixes are refuted about 2.5 times more often than findings, so nothing is applied unverified. Local rounds reliably kill criticals and highs but do not empty a gate's queue of mediums, and guards that enumerate forbidden spellings never converge against arbitrary text.