requesting-code-review

Yes, pre-merge code review can validate implementations against plans by dispatching a reviewer subagent with the base and head SHAs along with the original plan or requirements. This ensures the code changes align with the intended design before reaching mainline branches.

The best way to catch design flaws and missing tests before merging is using a structured review checklist scoped to the exact git changes. This process evaluates code quality, architecture, testing coverage, and production readiness to prevent issues from propagating into production releases.

You can use a subagent to validate feature implementations by supplying the base SHA, head SHA, implementation description, and the original requirements. The subagent assesses the code changes against the plan to verify completeness and production readiness.

Pre-merge code review requires a git base and head SHA to scope the evaluation to the intended changes. Without these commit identifiers, the reviewer cannot isolate the specific code diff to assess code quality, architecture, and testing coverage.

To structure code review feedback for production readiness, categorize findings into Critical, Important, and Minor levels with specific guidance on fixes. This structured template ensures thorough validation of code quality, architecture, and testing coverage.