requesting-code-review

To get a code review before merging, provide a focused git diff range, a summary of the feature requirements, and the completed changes. The review evaluates plan alignment, code quality, and test coverage to determine merge readiness.

Validating code changes at a task checkpoint involves reviewing the focused diff range against the initial requirements. This structured evaluation assesses production readiness, architecture, and correctness to catch bugs early before proceeding.

A pre-merge code review groups feedback by severity, providing clear file-line references, impact explanations, and fix suggestions. This structured evaluation assesses production readiness and merge readiness.

Yes, you can use this code review for refactoring validation. It requires a focused diff range and a requirement summary to evaluate code quality, architecture, and production readiness before merging the refactored changes.

You need to provide a focused git diff range representing your completed changes, a summary of what was built, and the original requirements. This allows the review to assess correctness and merge readiness.

You should request a code review in your developer workflow after finishing a task, completing an important feature, refactoring code, or before merging to main. This verifies correctness and release risk before changes spread further.