codex-bridge

# Codex Bridge

Call OpenAI's Codex CLI to get responses, reviews, or perform tasks.

## When to Use This Skill

Activate when the user says things like:
- "Ask Codex...", "Have Codex...", "Let Codex..."
- "Get GPT's opinion on...", "What does OpenAI think..."
- "Get a second opinion on..."
- "Have Codex review..."
- "Let Codex fix/refactor/implement..."

## How to Call Codex

**Find the script path first:**
```bash
# Marketplace install (most users):
CODEX_BRIDGE="$HOME/.claude/plugins/cache/saurun-marketplace/saurun/*/skills/codex-bridge/codex-bridge.mjs"

# Resolve glob to actual path:
CODEX_BRIDGE=$(ls -1 $CODEX_BRIDGE 2>/dev/null | head -1)
```

**Basic command (read-only):**
```bash
node "$CODEX_BRIDGE" "<prompt>" --working-dir "<project-path>"
```

**With file modification capabilities:**
```bash
node "$CODEX_BRIDGE" "<prompt>" --full-auto --working-dir "<project-path>"
```

**CRITICAL:** Always pass `--working-dir` with the project directory so Codex can read files. Without it, Codex runs in its install location and can't access your project files.

## Decision Logic

### Use READ-ONLY mode (no flags) when:
- User wants an opinion, explanation, or review
- User wants to compare perspectives
- User is asking questions
- Task is about analysis, not modification

### Use `--full-auto` mode when:
- User explicitly asks Codex to fix, refactor, or implement something
- User wants Codex to make changes to files
- Words like "fix", "refactor", "implement", "update", "change" are used

## Handling File Reviews

When user wants Codex to review a file:

1. Read the file content first using the Read tool
2. Include the content in the prompt to Codex
3. Structure the prompt clearly

Example:
```bash
node "$CODEX_BRIDGE" "Review this planning document and provide feedback on feasibility, risks, and suggestions:

---
[FILE CONTENT HERE]
---" --working-dir "/path/to/project"
```

## Response Format

Always present Codex's response clearly:

**For opinions/reviews:**
> **Cod