requesting-code-review

To review a git diff, provide a base-to-head range, an implementation summary, and the explicit requirements. The review checks plan alignment, code quality, architecture, testing, and production readiness to return a merge readiness verdict.

Checking merge readiness involves evaluating completed code changes against stated requirements to identify gaps or risky design choices. This produces a clear verdict with strengths, issues, and recommendations so teams can decide whether to proceed.

Yes, automated code review applies to feature implementation, bug fixes, refactors, and pre-merge checks. It requires a concise implementation summary and explicit requirements to assess plan alignment, code structure, and production readiness.

You need to provide a concise implementation summary, explicit requirements, and a base-to-head git diff range. This allows the review to assess plan alignment, code quality, architecture, testing, and production readiness.

Code reviews miss requirement alignment gaps when they lack explicit requirements to check against. Supplying a concise implementation summary and a clear plan ensures the review accurately verifies scope alignment and identifies missed tasks.