adversarial-review

Diagnose root causes of stalled code reviews and propose alternative directions.

Updated Apr 13, 2026

Search Tags:#iteration #code-review #software-engineering #root-cause-analysis #adversarial-review #design-analysis #alternative-direction

Ready to run

npx skills add https://github.com/moonseokchoi-kr/moon-harness --skill adversarial-review-moonseokchoi-kr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adversarial-review
Source: https://github.com/moonseokchoi-kr/moon-harness/tree/main/skills/adversarial-review
Command: npx skills add https://github.com/moonseokchoi-kr/moon-harness --skill adversarial-review-moonseokchoi-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When reviews stall or fail to address the core direction, this skill performs a fundamental critique to pivot the approach and uncover root causes.

Core Features & Use Cases

Fundamental critique: challenges core assumptions and identifies misaligned design choices.
Structured iteration: guides rework by proposing concrete alternative directions and evaluation criteria.
Use Case: applying to a stalled PR where feedback recurs without progress, and the team needs a new strategic direction.

Quick Start

Provide the latest PR diff and design brief to the adversarial-review agent to receive a redirected approach.

Frequently Asked Questions about adversarial-review

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

FAQPage Schema

How do I resolve a stalled code review where feedback keeps recurring without progress?▼

A stalled code review requires fundamental critique to diagnose root causes of persistent feedback loops. Providing the PR diff and design brief allows an adversarial review to output structured critique levels and concrete alternative directions for implementers.

What is an adversarial review in software engineering?▼

Adversarial review is a fundamental critique process that challenges core assumptions and identifies misaligned design choices in software engineering. It diagnoses root causes of persistent code review failures to pivot the approach and uncover alternative directions.

How do I perform a root cause analysis on a failing pull request?▼

To perform root cause analysis on a failing PR, provide the latest diff and design brief to an adversarial review process. This outputs structured critiques identifying fundamental, structural, or nit-pick level issues and proposes alternative approaches.

Can I use a structured critique to redirect a stalled design analysis?▼

Yes, you can use structured critique to redirect a stalled design analysis by challenging core assumptions. It applies to design requirements where feedback stalls, providing concrete alternative directions and evaluation criteria for implementers.

When should I not use an adversarial review for code review?▼

You should not use adversarial review for code review when feedback is actively progressing and addressing the core direction. It is specifically designed for stalled PRs where feedback recurs without progress and requires a new strategic direction.