requesting-code-review

Automating code review feedback involves dispatching a dedicated review subagent to examine changes before they cascade. This catches issues early by providing structured feedback with severity levels and clear remediation steps.

To request a git code review, you must provide explicit inputs: what was implemented, the plan or requirements, base SHA, head SHA, and a description. These inputs guide the reviewer with a structured template for precise examination.

You should request a code review after completing each task, after finishing major features, and before merging to main. This ensures readiness for review and integration, catching issues before they cascade into larger problems.

Early code review integrates with standard git pull request workflows by capturing base and head SHAs to define the exact change scope. It dispatches a subagent to examine the diff and guides reviewers using a structured template with severity categorization.

The best way to structure code review feedback is using a template with severity levels and clear remediation steps. This categorizes issues by importance, ensuring reviewers can prioritize fixes before changes are merged into main.