codex review: a review on demand
The work that most needs a second reader is the work nobody watched. Codex has a review that does not touch your files.
codex review --helpRun a code review non-interactively
Usage: codex review [OPTIONS] [PROMPT]
Arguments:
[PROMPT]
Custom review instructions. If `-` is used, read from stdinNo prompt gives you the default review. A prompt makes it a specific one, which is where most of the value is: check error handling on the new endpoints beats review this every time.
What it does not do
It reports findings and leaves your working tree alone. In the app the same thing is /review, with a choice between reviewing against a base branch and reviewing uncommitted changes, and it needs the project to be a git repository.
That separation matters. A review that also fixes things is two jobs at once, and you cannot tell which findings you agreed with.
Where it fits
- Before you open a pull request, on your own uncommitted work.
- In CI, through
codex exec review, so unattended changes still get read. - On somebody else's branch, with a read-only profile, since a review never needs to write.
That last one is worth doing on purpose. A review run under -P :read-only from lesson 4 cannot change anything even if it decides it would like to.
- Run
codex reviewon your current changes with no prompt, then with one. - Run it again under
-P :read-onlyand confirm nothing was touched.
Little by little, you're building something great.