Status
Gated Claude x Codex build loop for Claude Code: Codex plans and implements from one persistent thread, Claude approves the plan and reviews the diff. Zero deps, 20-test smoke suite.
npx -y skills add ozzaii/codex-claude-loop --skill statusAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 12 days oldThe repository was created 12 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Show every codex-claude-loop slug and where it stands (plan/review gates, impl marker, base)
SKILL.md
1.0 KB, as published. Nobody here has run it
Load the codex-claude-loop skill, source its lib, and run cl_status.
The PLAN and REVIEW columns show approve only when that approval is still valid for
the current state: the plan still hashes to what was approved, and the review still
matches this tree. A column showing the recorded word instead means the approval no
longer binds.
For each slug that is not fully approved, say in one line what the next action is: plan
needs reading, plan needs re-briefing, impl not run, impl failed, diff needs review,
blocking items need cl_revise, or the tree moved and needs re-review.
For a slug where both gates hold, say it is ready for cl_release. Do not claim it has
been released: this harness tracks gates, not deploys, so whether it shipped is something
you have to check in the project's own way (git log, tags, the deploy target).