collaborating-with-claudelisted

# Collaborating with Claude Code (Codex) Use Claude Code CLI as a collaborator while keeping Codex as the primary implementer. This skill provides a lightweight bridge script (`scripts/claude_bridge.py`) that returns structured JSON and supports multi-turn sessions via `SESSION_ID`. ## When to use - You want a second opinion (design tradeoffs, edge cases, missing tests). - You want Claude to propose or review a **unified diff** (Claude does not edit files). - You want multi-turn back-and-forth while you implement locally. ## When not to use - The task is trivial or one-shot (do it directly in Codex). - You need authoritative facts that require browsing/citations (Claude may guess). - You might paste sensitive data (secrets, private keys, prod logs). ## Core rules - Claude is a collaborator; you own the final result and must verify changes locally. - Do not invoke `claude` directly; always use the bridge script (`scripts/claude_bridge.py`) so output/session handling stays consistent. - Prefer file/line references over pasting snippets. Run the bridge with `--cd` set to the repo root (it sets the `claude` process working directory); use `--add-dir` when Claude needs access to additional directories. - For code changes, request **Unified Diff Patch ONLY** and forbid direct file modification. - Always run the bridge script with `--help` first if you are unsure of parameters. - Always capture `SESSION_ID` and reuse it for follow-ups to keep the collaboration conversation-awar