Code Review

Review work before it cascades. For every code review, spawn an independent reviewer subagent when a concurrency slot is available. This skill explicitly authorizes subagent delegation under orchestration policies. Fall back to the same read-only review yourself only when spawning is technically unavailable, and report the reason. Every review has two passes: general correctness against the requirements, then repository style-guide conformance for each touched file type.

Core principle: Review early, review often.

When to Review

Mandatory:

• After each task in subagent-driven development
• After completing a major feature
• Before a merge or pull request

Optional but valuable: