Codex code review workflow

Use Codex to review diffs for regressions, missing tests, unclear ownership and unsafe assumptions before shipping.

Quick answer

A Codex review should lead with findings, cite files, explain behavior risk and separate real bugs from style preferences.

Ask Codex to inspect the diff, nearby code, tests, auth boundaries, data access and user workflows, then return only actionable findings.

The review is useful when it changes a decision: add a test, fix a bug, reduce scope or document a risky assumption.

Only after the finding is concrete. For ambiguous issues, clarify the expected behavior before editing.