review-codex

You are orchestrating an adversarial security review of the current branch using an OpenAI model. Claude hydrates the prompt with codebase context, then dispatches to a different model for a cold-start review — different model, different blind spots.

Phase 0: Prerequisites

Run these checks sequentially. Stop at the first failure.

1. Check if OPENAI_API_KEY is set:

   echo "${OPENAI_API_KEY:+set}"
   

   If NOT set, print:

   review-codex: OPENAI_API_KEY not set.
   
   To use this command:
     export OPENAI_API_KEY=sk-...
   
   Or add it to your shell profile (~/.zshrc, ~/.bashrc).
   This command requires an OpenAI API key to dispatch reviews to a different model.
   

   STOP.

   If set:

   • API_BASE="https://api.openai.com/v1"
   • MODEL="gpt-4.1" (or override with REVIEW_CODEX_MODEL env var if set)
   • Print: Backend: OpenAI API (direct)

2. Get the diff stat:

   git diff main --stat
   

   If empty (no changes vs main), print:

   review-codex: No changes to review (branch matches main).
   

   STOP.

3. Print header:

   Review-Codex: <branch> @ <directory> (<model>)
   

   Use git branch --show-current and pwd for the values.

Phase 1: Gather Context

Collect all of the following. Run independent steps in parallel where possible.

1a. Git data

• git diff main — full diff (save to variable for Phase 2)
• git diff main --name-only — affected file list

1b. Codebase reconnaissance (best-effort)

Search the codebase for context about the changed areas:

1. Read CLAUDE.md if it exists — extract architecture section and any security rules
2. For the most-changed files, read surrounding context (imports, module structure)
3. If Pharaoh MCP tools are available, use get_codebase_map and get_blast_radius on the most-changed functions

1c. Large diff handling

If the diff exceeds 2000 lines:

• Filter to only security-relevant files: anything in paths containing auth, crypto, db, api, middleware, config, token, session, oauth, webhook, secret, key, password, login, permission, tenant, admin, or handler/route files.
• Print a note: Large diff (N lines). Filtered to M security-relevant files. Run on a smaller branch for full coverage.
• Use the filtered diff for the prompt.