codex-claude-loop
Use when driving a gated build loop where Claude orchestrates and Codex CLI implements — Claude plans and judges, Codex…
Send an additional request to the exact Codex session for an implemented codex-claude-loop lane, sequenced behind its writer lock
Claude Code
$ npx -y skills add ozzaii/codex-claude-loop --skill prompt --agent claude-code
Codex
$ npx skills add ozzaii/codex-claude-loop --skill prompt -a codex -y
Cursor
$ npx skills add ozzaii/codex-claude-loop --skill prompt -a cursor -y
Gemini CLI
$ npx skills add ozzaii/codex-claude-loop --skill prompt -a gemini-cli -y
GitHub Copilot
$ npx skills add ozzaii/codex-claude-loop --skill prompt -a github-copilot -y
OpenCode
$ npx skills add ozzaii/codex-claude-loop --skill prompt -a opencode -y
Windsurf
$ npx skills add ozzaii/codex-claude-loop --skill prompt -a windsurf -y
name: prompt description: Send an additional request to the exact Codex session for an implemented codex-claude-loop lane, sequenced behind its writer lock argument-hint: <slug> <additional request> allowed-tools: Bash, Read
Load the `codex-claude-loop` skill and source its bundled `lib/codex-claude-loop.sh`. Split `$ARGUMENTS` into the first word as the slug and the entire remaining text as one request, then call:
cl_prompt <slug> "<additional request>"
Do not call `codex exec resume` directly. `cl_prompt` resumes the stored session id, holds the same writer lock as `cl_impl` and `cl_revise`, and waits behind a running lane instead of starting a competing Codex process in the worktree.
The lane must already have a valid approved plan and a successful implementation marker. The follow-up is a writer phase: it clears any standing review approval, restores the implementation marker only after Codex exits cleanly, and prints Codex's final response. After it succeeds, re-review before release.
A gated build loop between Claude Code and Codex CLI. Codex writes the plan, Claude approves it, Codex implements that same plan from the same thread, Claude reviews the diff against it.
Use when driving a gated build loop where Claude orchestrates and Codex CLI implements — Claude plans and judges, Codex…
Check the codex-claude-loop substrate (codex CLI, jq, git, repo, verdict schema)
Show every codex-claude-loop slug and where it stands (plan/review gates, impl marker, base)
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.