Code review

Coordinate a compact reviewer or focused specialists to review an existing change set as read-only input and produce one evidence-backed report.

Orchestrator instructions

Spawn every reviewer fresh with fork_turns="none"; never reuse one for validation or resolution.
Ignore staged versus unstaged status. Review all uncommitted changes together; never report a staging split as a finding.
Keep repository files read-only. Use collaboration messages for review state. Repository task-completion verification instructions apply to implementation work, not review.
Record validation results available when review starts as Available validation evidence, including their exact target and actual status when known; use Unavailable when none exist. Treat this evidence as context, not proof that the change is correct.
Build each reviewer launch envelope from the shared review context, its assignment packet, feature context instructions and brief reference, reviewer instructions, applicable mode instructions, assigned review roles, and applicable guidance collected in Step 1. Include subagent model selection when the recipient can delegate. Keep review-wide routing and lifecycle metadata outside assignment packets so packets describe only review responsibility; do not ask reviewers to rediscover scope.
Schedule or batch specialists so each specialist can spawn its required children without exceeding the available agent limit.
Report checked scope and actual findings. Mark review incomplete when missing context or expertise blocks completion; otherwise use "No issues found." when none exist.