using-codex-collaborationlisted

Use proactively whenever the work involves substantial code changes (multi-file, core logic, architecture), a freshly written execution plan, a sticky bug that resists single-perspective diagnosis, or a non-obvious design decision that needs adversarial challenge — establishes when and how to bring Codex in as a reviewer (not as an executor). The ONLY channel is the persistent Codex pane reached via tmux (send-keys / capture-pane) — this holds even when Claude's own session is NOT running inside tmux (drive the tmux server externally; create a detached session if needed). Direct `codex` CLI invocation (codex exec etc.) is FORBIDDEN unless the user explicitly requests it, because it loses context. Covers locating/launching the Codex pane, the predefined collaboration scenarios (review-uncommitted, plan review, adversarial challenge, bug rescue), and the review⇄fix consensus loop that runs until Codex passes.
Jewel591/claude-with-codex · ★ 0 · Code & Development · score 70

Install: claude install-skill Jewel591/claude-with-codex

# Using Codex Collaboration ## Why this skill exists Codex is a **second perspective** — a reviewer that catches what the primary engineer missed. It is **not** a task-outsourcing endpoint. Hard line: - ✅ Codex does: plan review, code review, architecture review, independent bug diagnosis, sanity-checking design decisions. To do these it freely runs its own read tools (`git diff`, `git status`, `rg`, file reads) — that is expected and encouraged. - ❌ Codex does **not**: implement features, write new code, run the build/tests as a gate, finish work the primary engineer should finish. Treating "use Codex" as "outsource the task" is a misread, even if Codex has tokens to spare and the task is large or cross-file. **The primary engineer (you, Claude) finishes the work; Codex audits it.** This is a *behavioral* guarantee, enforced by your discipline — you are the sole writer to the working tree. Never ask Codex to edit/implement, and never proceed on the assumption that Codex changed files. After every Codex round, *you* make the edits. (Two narrow, whitelisted exceptions to the "Codex reviews, never does" line exist as sibling skills: `codex-image-gen` for producing image assets and `codex-computer-use` for GUI automation. Both cover one-off outputs that never enter the code-review loop; code work is never delegated.) ## The collaboration channel — the tmux Codex pane (ONLY entry point) There is a **persistent Codex TUI** running in a tmux pane, whose context accumulates