Reviewing Code

Adversarial review loop: reviewer finds issues → fixer resolves them → fresh reviewer verifies → repeat until clean. All findings and fixes happen locally — nothing is posted to GitHub.

Reference Files

File	Read When
`references/review-perspectives.md`	Spawning reviewer subagents — describes each review angle and what to look for
`references/confidence-scoring.md`	Scoring findings — rubric, thresholds, and false positive exclusions

How It Works

This is a fully autonomous process — the user is not involved until the review is complete or the manager needs help with something it can't resolve on its own.

The manager (you) orchestrates the loop between two roles:

reviewing-code

Reviewing Code

Reference Files

How It Works