Paths/Codex Engineer/Review & Guardrails / The Review Pass
Review a Diff Like a Reviewer
A review is a structured argument, not a feeling. Write the format your review notes follow so the findings are actionable.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/codex/review-notes.md exists○
- The notes state what changed○
- The notes state the risk and what has to be tested○
02Walkthrough
1 of 4 revealed- 01
Write the change summary
One paragraph. If you cannot write it, the diff is doing too much.
echo '# Review notes\n\n## What changed\n\nThe payment retry is scheduled by a new worker that polls the failed payments table every minute.' > ~/codex/review-notes.md - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list