adversarial-review

Reviews git diffs with two cross-vendor models that independently refute each other's findings.

4.0k|282|Updated Dec 2, 2024
One-click install
npx skills add https://github.com/basicmachines-co/basic-memory --skill adversarial-review-basicmachines-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/basicmachines-co/basic-memory/tree/main/.agents/skills/adversarial-review
Command: npx skills add https://github.com/basicmachines-co/basic-memory --skill adversarial-review-basicmachines-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo LLM code reviews suffer from self-ratification and confident false positives, so this Skill runs two reviewers from different model families (Claude and Codex/GPT) on the same diff and has each try to refute the other's findings, reporting only cross-examined results ranked by confidence. ## Core Features & Use Cases - Cross-vendor independent review: Claude and Codex/GPT each review the same git diff in isolation, one natively and one as a subprocess CLI, then emit structured findings matching a JSON schema. - Adversarial refutation phase: Each model attempts to refute the other's findings, and confidence (high, medium, low/contested) is assigned based on whether findings survive cross-examination. - Deterministic gates: Mechanical checks like lint, typecheck, and grep-based house-rule detection run before the models and are reported separately as facts. - Use Case: Before merging a feature branch, ask for an adversarial review against main to get a ranked table of findings where each item shows which model found it and whether the other model upheld or refuted it. ## Quick Start Run an adversarial review of my current branch against main and show me the ranked findings.

Frequently Asked Questions about adversarial-review

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

FAQPage Schema
How do I run a cross-model adversarial code review on my branch?▼

Invoke the skill from either Claude Code or Codex and it orchestrates both models automatically. It diffs your branch against a base ref (default main), has each model review independently, then cross-refutes findings and reports them ranked by confidence.

What is the difference between adversarial review and a single LLM code review?▼

A single model tends to ratify its own reasoning and produce confident false positives. Adversarial review uses two different model families that independently review the same diff and then attempt to refute each other's findings, so confidence reflects surviving cross-examination.

Can I scope the review to specific files or a different base branch?▼

Yes. Set the BASE input to change the ref being diffed against (default main) and the SCOPE input to a pathspec like src/basic_memory to narrow the review. Both are optional and independent of each other.

Does adversarial review automatically fix the issues it finds?▼

No. The skill is report-only by design. It presents a ranked table of findings with severity and confidence, then asks which findings you want fixed before any code is edited.

What happens if the other model's CLI is not installed?▼

The preflight check detects a missing codex or claude CLI and warns that the panel falls back to single-model review, which loses the cross-vendor benefit. You are asked whether to proceed or stop.

Why are lint and typecheck run before the model reviewers?▼

Models are statistically blind to negation rules like never do X, so mechanical house rules are enforced with deterministic tools instead. These gate hits are reported separately as high-confidence facts, distinct from model findings.