requesting-code-review

A pre-merge code review validates completed changes against requirements by performing systematic self-review, diff inspection, and test verification. It applies to major features, bug fixes, and refactors to ensure correctness and readiness before integrating to main.

Validating subagent-driven development handoffs requires a fresh reviewer to perform systematic self-review, diff inspection, and test verification. This fresh perspective catches defects and quality gaps the original developer missed before the code is merged.

Checking completed code for security, performance, and edge cases requires explicit assessment during a systematic self-review. You inspect the diff for vulnerabilities, verify test coverage for boundary conditions, and validate efficiency before merging to main.

Pre-merge validation works for major features, bug fixes, and refactors. It applies to any completed code change where correctness, test coverage, security, and maintainability matter, catching defects and requirement mismatches before integration.

Dispatching a fresh reviewer perspective uncovers defects and quality gaps you may miss during self-review. A new set of eyes systematically inspects the diff and verifies tests without prior bias, reducing late-stage bugs before integration.