adversarial-reviewer

Name: adversarial-reviewer
Availability: InStock
Author: andreicr1

Identify failure modes in code changes through adversarial scenario construction.

Updated Mar 14, 2026

Search Tags:#code-review #risk-analysis #adversarial-review #abuse-cases #failure-scenarios #assumption-violation #cascade-construction

Ready to run

npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill adversarial-reviewer-andreicr1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adversarial-reviewer
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/adversarial-reviewer
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill adversarial-reviewer-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conditional code-review persona that identifies and constructs failure-inducing scenarios to reveal brittleness in code changes, rather than merely checking for conformance.

Core Features & Use Cases

Assumption violation scenarios: Crafts inputs and environmental conditions that violate implicit data shape, timing, or ordering assumptions to trigger unexpected behavior.
Composition and contract analysis: Traces cross-component interactions to expose contract mismatches, shared-state mutations, and misaligned error handling.
Cascade construction & abuse cases: Builds multi-step failure chains to surface recovery weaknesses and edge-case exploitation patterns.
Risk signaling in high-stakes domains: Prioritizes findings based on keywords like authentication, payments, data mutations, or external APIs.

Quick Start

Provide a structured adversarial review for the given code diff, outlining failure sequences and risk signals.

Frequently Asked Questions about adversarial-reviewer

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

FAQPage Schema

What is adversarial code review and how does it uncover failure scenarios?▼

Adversarial code review actively tries to break code changes by constructing failure-inducing scenarios. It exposes brittle edges by applying assumption violations, composition failures, and abuse-case analysis to reveal unexpected behavior rather than just checking for standard conformance.

How do I find boundary conditions and assumption violations in large code diffs?▼

To find assumption violations in large diffs, apply an adversarial review persona that crafts specific inputs and environmental conditions. This targets implicit data shape, timing, or ordering assumptions to trigger unexpected behavior and stress the implementation.

What is the best way to review high-risk code changes in domains like authentication and payments?▼

The best way to review high-risk domain changes is using targeted risk signaling. Prioritize adversarial review findings based on keywords like authentication, payments, data mutations, or external APIs to focus on the most critical failure sequences.

How do I trace cross-component contract mismatches and shared-state mutations during a risk analysis?▼

Trace cross-component interactions by applying composition and contract analysis during your risk analysis. This exposes contract mismatches, shared-state mutations, and misaligned error handling across components within the code diff.

Can I use cascade construction to surface recovery weaknesses in multi-step failure chains?▼

Yes, cascade construction builds multi-step failure chains to surface recovery weaknesses. By chaining individual failures together, this abuse-case analysis exposes edge-case exploitation patterns and highlights where the implementation fails to recover properly.