requesting-code-review

To request an evidence-driven code review, you dispatch a formal reviewer with a structured template covering scope, success criteria, architecture boundaries, and fresh evidence. This verifies implementation quality before merging high-risk work to main.

An evidence-first code review is an advisory process that focuses on the work product by requiring structured outputs, baseline alignment, and concrete evidence rather than acting as a simple completion gate.

You need to run a formal code review after each subagent-driven task or major feature completion, and specifically before merging to main, to surface findings and verify product baseline alignment.

A code review checklist for architecture verification should include scope, success criteria, product baseline, architecture boundary, fresh evidence, compatibility boundaries, retirement notes, reviewer responsibilities, and advisory status.

No, this code review workflow does not act as a completion gate. It is designed to be advisory and evidence-oriented, preserving the reviewer's context while focusing strictly on the work product.

Yes, while it applies after subagent-driven tasks, the structured review process can be used to verify any major feature completion by gathering implementation details, plans, and baseline references to dispatch a reviewer.