requesting-code-review

Code review before merging is enforced via a repeatable self-review checklist that validates spec compliance, code quality, tests, and final verification. This structured process catches missed requirements and edge cases early in the lifecycle.

A self-review checklist for merge preparation is a systematic workflow that validates spec compliance, code quality, and test coverage. It ensures end-to-end verification and risk assessment are completed before a PR is declared ready.

To verify spec compliance and code quality before declaring a task complete, gather context and inspect artifacts through an end-to-end verification workflow. This mitigates quality gaps and ensures all changes are well-understood and documented.

Yes, this code review checklist works for small Git fixes as well as major features. It is applicable across all Git-based workflows, enforcing systematic review regardless of the software development task's scale.

You should run a code review checklist in your development workflow after completing each task or feature in your execution plans. Running it at this stage enforces post-change verification and risk assessment before initiating a PR.