requesting-code-review

Pre-merge code review requires a base and head commit comparison to evaluate recent implementation changes. The workflow dispatches a production readiness assessment across your git range, checking code quality, architecture, and testing before you merge.

Production readiness assessment evaluates code quality, architecture, testing, and documentation together before shipping. It provides severity-ranked findings to help you decide what must be fixed before releasing a major feature or bug fix to production.

Code review workflows apply to feature delivery, refactors, and bug fixes across task batches. The process aligns your implementation against original requirements and checks edge cases to ensure the changes are safe to release.

Verifying implementation against requirements involves comparing your head and base commits to detect requirement drift. The review generates severity-ranked findings covering code quality and production readiness to catch missed bugs and weak tests.

Catching code quality issues before merging requires a severity-ranked review of your git diff. This pre-merge validation process evaluates architecture and testing completeness to reduce the risk of releasing critical bugs to production.

A base and head commit comparison is required to perform a git diff code review. This commit range provides the necessary implementation changes for requirement alignment and severity-ranked findings across your task batches.