requesting-code-review

To automate a code review before a pull request merge, you can trigger a subagent to validate changes against your plan. This workflow requires a git base and head SHA, plus a concise description of what was implemented.

A pre-merge code review workflow dispatches a subagent to assess changes for quality and alignment with planned requirements. It consolidates context and surfaces categorized issues to catch regressions before integration.

You need to provide the git base and head SHA, a concise description of what was implemented, and a matching plan to compare against your requirements. This context allows the review subagent to validate the changes accurately.

Yes, you can use an automated code review subagent for task-by-task development. After completing a specific task, you trigger the review flow with a short summary of the implementation and the intended plan.

Automating code review structures feedback and surfaces critical issues prior to opening a pull request, but it functions as a pre-merge verification step. It consolidates findings and ties them back to requirements to support manual checks.

You should trigger an automated code review after completing a feature or task, prior to opening a pull request. This timing allows you to surface critical issues and catch regressions before integration.