requesting-code-review

You can automate code review requests by using a structured template that pulls base and head SHAs and dispatches a code-reviewer subagent. This workflow ensures your changes align with requirements before merging to main.

A code review request template requires WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. Populating these placeholders ensures the code-reviewer subagent receives complete context for quality assurance.

Request a code review after completing tasks, implementing major features, or before merging to main. Initiating reviews at these stages catches issues early and verifies that changes meet production requirements.

The code-reviewer subagent uses base and head SHAs to identify the exact range of code changes for evaluation. Pulling these commit references automates the review dispatch process to ensure production-ready changes.

No, this code review workflow requires base and head SHAs to function correctly. The structured template depends on these git commit references to dispatch the code-reviewer subagent and evaluate the specific changes.

The best way to standardize code review requests is to enforce a structured workflow with templates. Using predefined placeholders for implementation details and git SHAs ensures consistent quality assurance before merging.