requesting-code-review

Automate code review by dispatching a code-reviewer subagent to assess recent work for production readiness before merging to main. The subagent evaluates changes against the original plan and requirements to provide targeted feedback.

Subagent-driven code review requires precise context including what was implemented, the plan or requirements, and the base and head SHAs. Providing this context enables the subagent to target feedback specifically to the recent changes.

Request a code review after completing each task, after implementing major features, or before merging to main. Applying reviews at these stages catches issues early and drives fixes before proceeding further in the workflow.

A code-reviewer subagent evaluates production readiness by assessing recent work against provided context like requirements and SHAs. It captures actionable feedback and categorizes issues by severity to drive necessary fixes.

Yes, you can categorize issues by severity when reviewing code changes. The subagent captures actionable feedback and sorts issues by severity, allowing developers to prioritize and drive fixes before proceeding to production.

The best way to get early feedback is dispatching a code-reviewer subagent after completing a task or major feature. This provides precise, targeted feedback on changes before merging to main.