codex-review

Codex Code Review + Double-Check

Invoke the Official Codex companion's review, then apply Claude's independent evaluation to every finding.

Step 1: Pre-flight — Companion Check

CODEX_COMPANION=$("${CLAUDE_PLUGIN_ROOT}/scripts/resolve-companion.sh")

If resolve fails: direct to /codex-setup immediately. Do NOT fall back to a Claude-only solo review.

Step 2: Execute via Companion Script

Use the $CODEX_COMPANION resolved in Step 1:

node "$CODEX_COMPANION" review --wait $ARGUMENTS

If $ARGUMENTS is empty, pass no args — companion auto-detects scope (uncommitted or branch).

Timeout: 300000ms (5 minutes).

If command fails:

Error	Action
"not authenticated" in stderr	Auth required → suggest codex login
Other error	Show raw error, don't retry silently

Step 3: Double-Check

Read ${CLAUDE_PLUGIN_ROOT}/references/evaluation.md.

For each finding in the Official review output:

1. Read the actual code at the file/line Codex mentions
2. Classify: Agree / Disagree / Nuance — with evidence
3. If Codex mentions a file or function that doesn't exist, flag as false positive

Step 4: Report

Present to user:

1. Codex findings (verbatim from Official output)
2. Claude's evaluation per finding
3. Agreement level (High / Partial / Disagreement)
4. Additional findings Claude spotted that Codex missed

Step 5: Save

mkdir -p "${CLAUDE_PLUGIN_DATA}/reviews"

Save to ${CLAUDE_PLUGIN_DATA}/reviews/review-<YYYYMMDD-HHMMSS>.md using format from evaluation.md.

Gotchas

• Do not auto-fix. Present findings, wait for user.
• Preserve Codex output verbatim. Evaluation comes after.
• Companion handles scope detection, job tracking, retry. Our job is evaluation only.
• Always pass --wait. Without it, companion prompts for foreground/background selection via AskUserQuestion, which disrupts our flow.