Codex Review, Git, Browser, and Automation

Use Codex for review, Git operations, recurring engineering tasks, and browser-assisted UI iteration.

45 min

3 sections

codex

review

git

automation

browser

01. Code review should be narrow and adversarial

Section 1 of 3

Codex review is most useful when you ask for prioritized defects, not generic feedback. Make it look for behavior regressions, missing tests, security mistakes, data loss, and edge cases. Then decide which findings are real before asking Codex to patch them.

text

Review this diff.
Prioritize only:
- behavior regressions
- auth or tenant isolation bugs
- data loss
- missing tests for changed behavior
- production observability gaps

For each finding, include:
- file
- exact risk
- why the current code fails
- minimal fix

Do not comment on naming or style unless it hides a real bug.

Codex Controls, Context, and Subagents

Claude Code Terminal Operating Model

Back to Course