subagent-vs-review

Runs bounded adversarial reviews with fresh subagents and a deterministic review governor.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ceasarXuu/AstartesSkills --skill subagent-vs-review-ceasarxuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-vs-review
Source: https://github.com/ceasarXuu/AstartesSkills/tree/main/skills/subagent-vs-review
Command: npx skills add https://github.com/ceasarXuu/AstartesSkills --skill subagent-vs-review-ceasarxuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding agents often validate their own work, creating self-reinforcing loops where generated code and generated tests confirm the same assumptions. This Skill introduces independent adversarial review with fresh, context-isolated subagents while preventing unbounded review loops, scope drift, and speculative repairs. ## Core Features & Use Cases - Fresh Adversarial Review: Spawns isolated reviewer subagents that receive only a neutral navigation packet and attack assumptions, failure paths, usability, and implementation completeness. - Deterministic Review Governor: Enforces a two-round automatic budget, evidence authority levels (E0-E4), scope-drift detection, and convergence checks before any repair or extra round. - Auditable Review Trail: Writes a structured Markdown report under /vs_review/ recording reviewer launches, findings, triage decisions, and closure status. - Use Case: After implementing a payment retry flow, run an adversarial review where a fresh subagent challenges concurrency and idempotency assumptions, then let the governor decide whether a single closure round is justified. ## Quick Start Ask the agent to run an adversarial subagent review of the current implementation before treating the task as complete.

Frequently Asked Questions about subagent-vs-review

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

FAQPage Schema
How do I run an adversarial code review with AI subagents?

Invoke the skill on your task and it spawns a fresh internal subagent that receives only a neutral review navigation packet, never the main agent's history or conclusions. The reviewer inspects target files directly and records blocking findings in a /vs_review/ report.

What is a review governor in an AI review workflow?

The review governor is a deterministic control layer that decides whether the workflow may continue, start a closure round, pass, stop for scope drift or insufficient evidence, or require a user decision. It enforces a two-round automatic budget and blocks speculative repairs.

What happens if internal subagents are unavailable in my agent runtime?

The skill searches for local CLI reviewers such as Claude, Codex, OpenCode, and Pi, then asks for explicit user approval before invoking one. If no verified and approved reviewer exists, the review stops and records blocked_due_to_review_unavailable.

How many review rounds does the skill run automatically?

Exactly two automatic rounds at most: one initial adversarial review and one focused closure review for accepted blocking findings. A third round requires explicit user approval after seeing a convergence reflection with remaining blockers and rollback options.

When should I not use adversarial subagent review?

Avoid it for trivial single-file changes where review overhead exceeds risk, since each round requires a fresh subagent session and a formal report. It is designed for work affecting architecture, state, data, security, or user-facing flows.