Automates a collaborative feedback loop between Claude Code and Codex to ensure high-quality code and architecture.
Install
mkdir -p .claude/skills/codex-claude-loop && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/181" && unzip -o skill.zip -d .claude/skills/codex-claude-loop && rm skill.zipInstalls to .claude/skills/codex-claude-loop
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Orchestrates a dual-AI engineering loop where Claude Code plans and implements, while Codex validates and reviews, with continuous feedback for optimal code qualityKey capabilities
- →Orchestrate multi-model validation loops
- →Generate cross-model feedback reports
- →Execute iterative refinement based on Codex reviews
- →Apply security and architectural linting to implementation
- →Document assumptions and edge cases
How it works
Manages a handoff cycle where one agent generates architecture/code and the second agent performs validation checks.
Inputs & outputs
When to use codex-claude-loop
- →Validating complex architectural plans
- →Reviewing code for security gaps
- →Debugging complex implementation steps
- →Ensuring high-quality output on critical tasks
About this skill
Codex-Claude Engineering Loop Skill
Core Workflow Philosophy
This skill implements a balanced engineering loop:
- Claude Code: Architecture, planning, and execution
- Codex: Validation and code review
- Continuous Review: Each AI reviews the other's work
- Context Handoff: Always continue with whoever last cleaned up
Phase 1: Planning with Claude Code
- Start by creating a detailed plan for the task
- Break down the implementation into clear steps
- Document assumptions and potential issues
- Output the plan in a structured format
Phase 2: Plan Validation with Codex
- Ask user (via
AskUserQuestion):- Model:
gpt-5orgpt-5-codex - Reasoning effort:
low,medium, orhigh
- Model:
- Send the plan to Codex for validation:
echo "Review this implementation plan and identify any issues:
[Claude's plan here]
Check for:
- Logic errors
- Missing edge cases
- Architecture flaws
- Security concerns" | codex exec -m --config model_reasoning_effort="" --sandbox read-only
- Capture Codex's feedback
Phase 3: Feedback Loop
If Codex finds issues:
- Summarize Codex's concerns to the user
- Refine the plan based on feedback
- Ask user (via
AskUserQuestion): "Should I revise the plan and re-validate, or proceed with fixes?" - Repeat Phase 2 if needed
Phase 4: Execution
Once the plan is validated:
- Claude implements the code using available tools (Edit, Write, Read, etc.)
- Break down implementation into manageable steps
- Execute each step carefully with proper error handling
- Document what was implemented
Phase 5: Cross-Review After Changes
After every change:
- Send Claude's implementation to Codex for review:
- Bug detection
- Performance issues
- Best practices validation
- Security vulnerabilities
- Claude analyzes Codex's feedback and decides:
- Apply fixes immediately if issues are critical
- Discuss with user if architectural changes needed
- Document decisions made
Phase 6: Iterative Improvement
- After Codex review, Claude applies necessary fixes
- For significant changes, send back to Codex for re-validation
- Continue the loop until code quality standards are met
- Use
codex exec resume --lastto continue validation sessions:
echo "Review the updated implementation" | codex exec resume --last
Note: Resume inherits all settings (model, reasoning, sandbox) from original session
Recovery When Issues Are Found
When Codex identifies problems:
- Claude analyzes the root cause
- Implements fixes using available tools
- Sends updated code back to Codex for verification
- Repeats until validation passes
When implementation errors occur:
- Claude reviews the error/issue
- Adjusts implementation strategy
- Re-validates with Codex before proceeding
Best Practices
- Always validate plans before execution
- Never skip cross-review after changes
- Maintain clear handoff between AIs
- Document who did what for context
- Use resume to preserve session state
Command Reference
| Phase | Command Pattern | Purpose |
|---|---|---|
| Validate plan | echo "plan" | codex exec --sandbox read-only | Check logic before coding |
| Implement | Claude uses Edit/Write/Read tools | Claude implements the validated plan |
| Review code | echo "review changes" | codex exec --sandbox read-only | Codex validates Claude's implementation |
| Continue review | echo "next step" | codex exec resume --last | Continue validation session |
| Apply fixes | Claude uses Edit/Write tools | Claude fixes issues found by Codex |
| Re-validate | echo "verify fixes" | codex exec resume --last | Codex re-checks after fixes |
Error Handling
- Stop on non-zero exit codes from Codex
- Summarize Codex feedback and ask for direction via
AskUserQuestion - Before implementing changes, confirm approach with user if:
- Significant architectural changes needed
- Multiple files will be affected
- Breaking changes are required
- When Codex warnings appear, Claude evaluates severity and decides next steps
The Perfect Loop
Plan (Claude) → Validate Plan (Codex) → Feedback →
Implement (Claude) → Review Code (Codex) →
Fix Issues (Claude) → Re-validate (Codex) → Repeat until perfect
This creates a self-correcting, high-quality engineering system where:
- Claude handles all code implementation and modifications
- Codex provides validation, review, and quality assurance
When not to use it
- →Simple, low-stakes coding tasks
- →Situations where speed is prioritized over validation
- →Non-code logic generation
Prerequisites
Limitations
- →Increased latency due to multiple passes
- →Requires context management between model handoffs
How it compares
It formalizes a multi-model feedback loop that prevents single-model hallucination or logic errors.
Compared to similar skills
codex-claude-loop side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| codex-claude-loop (this skill) | 13 | 9mo | Review | Advanced |
| python-testing-patterns | 77 | 2mo | Review | Intermediate |
| error-handling-patterns | 35 | 2mo | No flags | Intermediate |
| serena | 15 | 9mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by bear2u
View all by bear2u →You might also like
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
serena
massgen
This skill provides symbol-level code understanding and navigation using Language Server Protocol (LSP). Enables IDE-like capabilities for finding symbols, tracking references, and making precise code edits at the symbol level.
javascript-mastery
davila7
Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional programming. Use when explaining JS concepts, debugging JavaScript issues, or teaching JavaScript fundamentals.
find-bugs
davila7
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.
cursor-indexing-issues
jeremylongshore
Manage troubleshoot Cursor codebase indexing problems. Triggers on "cursor indexing", "cursor index", "cursor codebase", "@codebase not working", "cursor search broken". Use when working with cursor indexing issues functionality. Trigger with phrases like "cursor indexing issues", "cursor issues", "cursor".