name: codex-delegate description: | Use when the user wants a second opinion or review from Codex on code, docs, diffs, or design notes without modifying files. This includes implementation review, bug risk review, security review, and document clarity review through `codex exec`. Do NOT use for tasks that require file edits or direct implementation; keep this skill review-only. Trigger especially when the user says review with Codex, second opinion, delegate review, use codex, or check this diff or document.

Codex Delegate

Delegate review tasks to OpenAI Codex CLI using codex exec (non-interactive mode).

Command Pattern

codex exec -s read-only "<prompt>"

Required flags:

-s read-only - Always use read-only sandbox (review only, no file changes)

Optional flags:

-m <model> - Override model (default: configured in ~/.codex/config.toml)
-C <path> - Set working directory (must combine with --skip-git-repo-check if the target is outside a trusted git repo)
--skip-git-repo-check - Skip trusted git repository check. Required when reviewing files outside of a git repository (e.g., ~/.local/state/steering/)

Code Review

Construct a prompt that specifies the target files and review criteria.

Single file review

codex exec -s read-only "Review the implementation in src/auth.ts. Check for bugs, security issues, and adherence to best practices. Provide specific suggestions for improvement."

Multi-file / directory review

codex exec -s read-only "Review all files under src/api/. Focus on error handling, input validation, and API design consistency. List issues by severity."

Focused review (specific concern)

codex exec -s read-only "Review src/db/queries.ts specifically for SQL injection vulnerabilities and improper input sanitization."

Git diff review

codex exec -s read-only "Review the changes in the current git diff (staged and unstaged). Check for bugs, style issues, and potential regressions."

Document Review

README / docs review

codex exec -s read-only "Review README.md for clarity, accuracy, and completeness. Check that setup instructions are correct and examples work as documented."

Design doc review

codex exec -s read-only "Review docs/architecture.md. Check for logical consistency, missing considerations, and alignment with the actual codebase structure."

Execution in Claude Code

Run codex exec via the Bash tool. The final review output prints to stdout.

codex exec -s read-only "<review prompt>"

When reviewing files outside a git repo (e.g., ~/.local/state/steering/), add --skip-git-repo-check:

codex exec -s read-only --skip-git-repo-check -C /path/to/dir "<review prompt>"

If the output is long, use -o /tmp/codex-review.txt and read the file afterward.

Prompt Construction Guidelines

Be specific about scope - Name exact files or directories to review
State the review criteria - What to focus on (bugs, security, style, clarity)
Request structured output - Ask for categorized findings (e.g., by severity)
Provide context - Mention the project's language, framework, or conventions when relevant

Notes

codex exec streams progress to stderr and final output to stdout
The command exits automatically when the agent finishes
Requires Codex CLI to be installed and authenticated (codex in PATH)
Read-only sandbox ensures Codex cannot modify any files