requesting-code-review

Standardize code-review requests by automating a workflow that enforces documenting base/head SHAs, implementation details, the plan, and test results before merging. This ensures QA and compliance are met consistently.

A structured pull request code review should include the base and head SHAs, what was implemented, the planned requirements, and the test results. This provides a clear audit trail and guides reviewer feedback handling.

You need to trigger an automated code review workflow after completing each task, after finishing major features, or before merging to main. This timing safeguards quality and ensures changes are documented.

A subagent handles reviewer feedback by defining clear decision handling and acceptance criteria. This guides the reaction to feedback, ensuring issues are resolved and maintaining a traceable record for accountability.

Yes, you can use this code review workflow for quality assurance after major features. It supports requesting and documenting reviews at this stage to catch hidden issues and enforce compliance before merging.