Code Review

Review only changes introduced by the target diff. Prioritize defects that can affect behavior or safe delivery; omit generic style advice and pre-existing issues.

For separate review, this is the correctness-focused pass after ponytail-review; do not duplicate that complexity audit. For an explicitly recorded tiny combined review, also inspect unnecessary machinery in this pass. Simplicity never substitutes for correctness evidence.

Inputs

• Head and base refs plus final head SHA.
• Review mode: combined (tiny, policy-permitted) or separate; include its reason.
• Changed files, commits, and whether uncommitted changes are included.
• Brief, accepted plan, episode state, and relevant finding dispositions when part of Kickoff.
• Applicable repository instructions and PR title/body when available.

Stop if the diff is empty, the base cannot be determined, or unrelated staged changes make the review boundary unsafe.

Reviewer Selection

Use an isolated reviewer when the diff has material ambiguity, blast radius, consequence, irreversibility, novelty, or coordination cost. Assess those dimensions in the change's own domain—including user experience, visual systems, accessibility, compatibility, performance, data/security, and delivery—not by a backend-only checklist. For a tiny low-risk diff, a focused orchestrator review is sufficient unless repository policy requires independence.