requesting-code-review

To get a structured code review before a pull request merge, provide an implementation summary, the original plan, and the base and head git SHAs. The review organizes feedback into strengths, critical issues, minor issues, and a merge verdict.

Validating major feature delivery involves dispatching a focused review of the completed work against the original plan using the base and head git SHAs. This catches design mistakes and gaps before they cascade into later development tasks.

You need a refactoring checkpoint when you finish a task, deliver a major feature, or feel stuck during software development. It verifies completed work against requirements to prevent bugs from spreading before you proceed.

Yes, you can use a git diff range defined by base and head SHAs to check for design mistakes. Supplying the implementation summary and plan allows the review to focus on the exact changes and prevent issues from cascading.

This code review process requires no specific dependencies, but needs a concise implementation summary, the plan or requirements, and the base and head git SHAs to accurately review the diff for pre-merge validation.