requesting-code-review

To request a code review before merging, you provide the git base and head range, a summary of the implementation, and the corresponding plan or requirements. This prompts a structured review to catch defects and regressions.

A structured pre-merge code review works by comparing your git head and base ranges against the original requirements. It validates completed features, triages findings by severity, and identifies requirement gaps before the final merge.

Yes, you can use code review checks for task-by-task validation in subagent workflows. The process evaluates completed code changes incrementally, ensuring each task meets requirements and passes quality assurance before proceeding.

To start a pre-merge code review, you need a defined git base and head commit range, a structured summary of what was implemented, and the intended development plan or requirements to validate the diff.

The best way to handle actionable feedback is to triage findings by severity. You decide which defects to fix immediately to prevent regressions and which quality issues can wait before merging the pull request.

You should request a code review instead of merging directly after completing a task, major feature, or bug fix. This pre-merge validation step reduces regressions by catching requirement gaps and quality issues early.