requesting-code-review

Code review before a merge verifies completed changes against matching acceptance criteria using a base-to-head commit range, evaluating correctness, architecture, testing, and production readiness independently.

Yes, a subagent can check git commits for regressions by evaluating a focused context of the implemented work, the requirement source, and the specific commit range to assess production readiness.

An independent production-readiness check requires a clear implementation summary of the bug fix, the matching plan or acceptance criteria, and the base-to-head git commit range to inspect.

An independent code reviewer is needed after each task in subagent-driven development to verify that the completed changes match requirements and are safe to ship before merging.

Yes, the code review process works by dispatching a reviewer with focused context like the implementation summary and commit range, rather than relying on the full conversation history.