codex-collab
SolidUse when the user asks to invoke, delegate to, or collaborate with Codex on any task. Also use PROACTIVELY when an independent, non-Claude perspective from Codex would add value — second opinions on code, plans, architecture, or design decisions.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- Kevin7Qi
- Repository
- Kevin7Qi/codex-collab
- Created
- 5 months ago
- Last Updated
- 1 weeks ago
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
codex-collab
Ask Codex CLI for an explicitly requested, read-only second opinion on a bounded review, diagnosis, architecture, or comparison question.
codex
Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user explicitly asks for Codex to do it. Also covers how to prompt Codex.
using-codex-collaboration
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.