codex-reviewlisted

# Code review by Codex An independent reviewer that hasn't seen this conversation is genuinely useful: it won't inherit your assumptions about the change. Use it as a *second* pass, not a replacement for your own read. ## Pick the scope ```bash git -C <repo> diff # uncommitted, unstaged git -C <repo> diff --staged # staged git -C <repo> diff main...HEAD # whole branch vs main git -C <repo> diff --stat main...HEAD # size check first ``` Check the size before sending. Under ~1500 changed lines, pipe the diff in directly. Larger than that, point Codex at the files instead and let it read selectively — a giant pasted diff degrades the review. ## Run it Small or medium change — pipe the diff as the prompt body: ```bash { echo "Review this diff as a senior engineer on this codebase. Report findings grouped by severity (Critical / Major / Minor / Nit). For each: file:line, what's wrong, and the concrete fix. Focus on correctness, security, error handling, race conditions, and missed edge cases. Skip style unless it hides a bug. If you find nothing at a severity level, say so rather than inventing findings."; echo; git -C <repo> diff main...HEAD; } | codex-run -C <repo> --timeout 1200 - ``` Large change or a whole module — let Codex read the tree itself: ```bash codex-run -C <repo> --timeout 1800 \ "Review the changes on this branch versus main (run git diff main...HEAD yourself, and read the surrounding files for context). Repor