codex-review-code

Codex Code Review

Send code changes to Codex CLI for an independent code review. Codex has a built-in review subcommand optimized for this.

Workflow

Step 1: Determine Review Scope

Parse the user's request to determine what to review:

• Uncommitted changes (default): No specific files or branch mentioned. Review all staged and unstaged changes.
• Branch comparison: User mentions a branch name (e.g., "review against main"). Use --base <branch>.
• Specific commit: User mentions a commit SHA. Use --commit <sha>.
• Specific files: User lists file paths. Concatenate and pipe to codex.

If there are no uncommitted changes and no specific scope was given, fall back to reviewing the last commit with --commit HEAD.

Step 2: Execute Codex Review

Use a 5-minute Bash timeout (300000ms) for all commands.

For uncommitted changes:

codex exec review --uncommitted --ephemeral -o /tmp/codex-code-review.md

For branch comparison:

codex exec review --base <branch> --ephemeral -o /tmp/codex-code-review.md

For a specific commit:

codex exec review --commit <sha> --ephemeral -o /tmp/codex-code-review.md

For specific files:

cat <file1> <file2> ... | codex exec --ephemeral -o /tmp/codex-code-review.md \
  "Review this code for:
- Bugs and logic errors
- Security vulnerabilities (injection, overflow, resource leaks)
- Design issues and code smells
- Missing error handling
- Performance concerns

Be specific. Reference line numbers and function names in your feedback."

Step 3: Present Results

Read /tmp/codex-code-review.md and present the review to the user.

Format the output with a clear header:

## Codex Code Review

<review content>

Clean up the temp file:

rm -f /tmp/codex-code-review.md

Error Handling

• If codex is not found: inform the user to install Codex CLI
• If no changes to review: inform the user that the working tree is clean
• If codex returns an error: show the error and suggest checking authentication (codex login)