Claudex Loop
Harden a plan with independent Claude/Codex review, then optionally build and...
Install
npx skills add chaseai-yt/claudex-loop --skill claudex-loop -g -a claude-code -y- Repository
- chaseai-yt/claudex-loop3.3k
- Category
- AI and agents
- Updated
- 21d ago
- License
- See repository
- Context cost
- Mediumabout 2,405 tokens
- Runs scripts
- Yes, review before use
What it does
Harden a plan with independent Claude/Codex review, then optionally build and cross-inspect it. Start in either Claude Code or Codex: the host plans and the other provider reviews. Use for claudex this plan, claudex-loop, or the legacy crucible trigger; not for trivial edits.
Claudex Loop
The current conversation owns requirements, planning and coordination. The other provider reviews the plan. Either provider can build; the provider that did not build inspects the final code in a fresh session.
Resolve roles once
Identify the actual host from your runtime, not PATH, installed skills, model-name guesses, or the repository. Both CLIs may be installed. Use host=claude in Claude Code and host=codex in Codex. If the runtime identity is unavailable, ask which host the user is using once.
| Host | Requirements and plan | Plan reviewer | Default builder | Final inspector |
|---|---|---|---|---|
| Claude Code | Current Claude session | Codex | Claude | Fresh Codex session |
| Codex | Current Codex session | Claude | Codex | Fresh Claude session |
Honor builder=claude|codex. The inspector is always the other provider. The host remains coordinator even when the other provider builds. To swap the planner, start the conversation in the other host; do not pretend a CLI reviewer is the user's planning conversation.
Model selection is independent of provider roles. Preserve the host's selected model. Review/build CLI calls inherit their own configuration unless reviewer_model, builder_model, or inspector_model is supplied; map these to the runner's --model for that invocation. Apply an explicit *_effort similarly. Fable 5.1 and GPT-6 Astra are suitable explicit choices, not mandatory pins. A model in the host UI does not prove which model a separate CLI will use. Report requested and observed model information separately; report an unresolved CLI default honestly. Never silently fall back to another model/provider on a failure.
Read the runtime reference before launching a CLI. Resolve its runner relative to this installed SKILL.md, never relative to the project being reviewed. Use absolute paths when launching it.
