adversarial-review

Coordinate two reviewers to identify defects and invariant violations in code.

4|Updated Jan 14, 2026

Search Tags:#code review #security #adversarial review #defect detection #parallel review

Ready to run

npx skills add https://github.com/oalders/kitchen-sink --skill adversarial-review-oalders

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/oalders/kitchen-sink/tree/main/skills/adversarial-review
Command: npx skills add https://github.com/oalders/kitchen-sink --skill adversarial-review-oalders

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill facilitates a competitive code review process, ensuring thorough examination of code by two reviewers working simultaneously to identify serious issues and maintain focus on the intended scope.

Core Features & Use Cases

Competitive Review: Two reviewers compete to find defects, fostering a more rigorous review process.
Scope Discipline: Ensures that the review remains focused on the intended scope and invariants.
Use Case: Ideal for reviewing complex patches or changes where a thorough examination is crucial, such as security updates or architectural changes.

Quick Start

Invoke the adversarial-review skill with the scope details and work to be reviewed, e.g., adversarial-review --invariants "user authentication" --threat-model "SQL injection" --out-of-scope "feature proposals" --work "/path/to/patch"

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 competitive code review to find security defects?▼

A competitive code review assigns two reviewers to independently examine the same codebase simultaneously, racing to identify security defects and invariant violations to maximize defect detection coverage.

What is an adversarial review and when do I need it?▼

An adversarial review is a parallel defect detection process where two reviewers compete to find serious issues. You need it when reviewing complex patches, security updates, or architectural changes requiring rigorous examination.

How do I define the scope for a parallel code review?▼

You define the scope for a parallel code review by specifying invariants, threat models, out-of-scope items, and the work path. This scope discipline ensures reviewers focus strictly on intended functionality and security.

Does this competitive review approach work for general feature proposals?▼

No, this competitive review approach is not suited for general feature proposals. It targets complex patches and security updates where maintaining strict focus on invariants and threat models is crucial for defect detection.

What is the best way to detect invariant violations in a complex patch?▼

The best way to detect invariant violations in a complex patch is using a parallel review process with two independent reviewers. This competitive approach ensures thorough examination and maintains focus on the intended scope.