requesting-code-review

A structured pre-merge code review anchors assessments to the actual git diff by comparing HEAD with BASE. It highlights differences that matter and validates changes against explicit requirements before merging to main.

Diff-driven code review is a structured process validating changes against actual git diffs and explicit requirements. You need it during major feature work, refactors, or bug fixes across any repository before PRs to main.

Run a structured pull request review in Codex by following a step-by-step workflow guidance checklist. This involves using placeholder templating for implemented features and referencing the plan to ensure production-readiness before merging.

Yes, this code review approach works for refactors and bug fixes. It defines mandatory and optional review triggers to ensure consistency, rigorously validating changes against explicit requirements and actual git diffs.

Diff-driven code review for pull requests is limited to evaluating the provided git diff and explicit requirements. It requires placeholders for what was implemented and a plan reference to satisfy the structured production-readiness checklist.