name: coding-workflow description: Code with Claude Code, review with Codex, then address review with Claude Code. Use for all coding tasks — writing, refactoring, building features, fixing bugs. metadata: { "openclaw": { "emoji": "🔄", "requires": { "allBins": ["claude", "codex", "gh"] } }, }

Coding Workflow: Build → Review → Address (via PR)

Three-phase workflow using GitHub PRs for all coding tasks:

1. Build — Claude Code writes/modifies the code on a feature branch
2. Review — Codex reviews via codex review, findings go on the PR
3. Address — Claude Code addresses review feedback, commits detail what Codex recommended

Phase 1: Build (Claude Code)

Create a feature branch and use Claude Code to do the coding:

cd <project-dir> && git checkout -b <feature-branch>
claude -p --dangerously-skip-permissions "<task description>"

• Always use PTY mode (pty: true)
• Use --dangerously-skip-permissions for non-interactive execution
• For longer tasks, run in background and monitor with process tool

After Claude Code finishes, commit and push:

cd <project-dir> && git add -A && git commit -m "<descriptive message>" && git push -u origin <feature-branch>

Then open a PR:

cd <project-dir> && gh pr create --title "<PR title>" --body "<description of changes>" --base main

Phase 2: Review (Codex)

Run Codex review against the base branch:

cd <project-dir> && codex review --base main "Review thoroughly: bugs, security, performance, style, edge cases. Be specific."

Or review uncommitted changes:

cd <project-dir> && codex review --uncommitted

Capture the full review output. This goes into the PR as a comment AND into the next commit message.

Post review findings as a PR comment:

cd <project-dir> && gh pr comment --body "## Codex Review

<paste review output>"

• Codex uses gpt-5.3-codex with high reasoning effort (configured in ~/.codex/config.toml)
• For large reviews, run in background

Phase 3: Address Review (Claude Code)

Feed the Codex review back to Claude Code:

cd <project-dir> && claude -p --dangerously-skip-permissions "A code review found the following issues. Address ALL of them:

<paste codex review output>

Fix every issue mentioned. If a suggestion doesn't make sense, explain why you're skipping it."

Commit with Codex recommendations in the message:

cd <project-dir> && git add -A && git commit -m "Address Codex review findings

Codex recommended:
- <finding 1>: <what was done>
- <finding 2>: <what was done>
- <finding 3>: <skipped — reason>
..." && git push

The commit message MUST detail what Codex found and how each item was addressed or why it was skipped.

Phase 4: Merge

After review fixes are pushed:

cd <project-dir> && gh pr merge --squash --delete-branch

Then switch back to main:

cd <project-dir> && git checkout main && git pull

Timing Expectations

Claude Code and Codex are slow by design — they read files, think deeply, and make multiple edits. This is normal:

• Claude Code (build): 3–8 minutes for medium tasks, 10+ for large refactors
• Codex (review): 2–5 minutes depending on diff size and reasoning effort
• Don't panic-poll. Check file modification times or git diff --stat every 60–90 seconds at most
• Don't kill early unless CPU is 0% for 2+ minutes with no file changes — they may just be thinking
• PTY output buffering means you often see no output until the process completes — this is normal, not a hang

When running in background, a good pattern:

1. Start the process
2. Tell the user it's running and will take a few minutes
3. Check progress once after ~90 seconds (file changes, process status)
4. Then poll at longer intervals (~2 min) until completion
5. Resist the urge to check every 6 seconds like an anxious parent

Workflow Notes

• Always use feature branches — never commit directly to main
• PR comments preserve the review trail — Codex findings are documented on the PR
• Commit messages detail Codex recommendations — every fix commit lists what was found and how it was addressed
• If Codex review is clean (no issues), skip Phase 3 and merge directly
• For background tasks: use the wake trigger pattern from the coding-agent skill
• Always work in the project directory, never in ~/clawd/

Quick Reference

| Phase | Tool | Key Command | |-------|------|-------------| | Build | Claude Code | claude -p --dangerously-skip-permissions "task" | | PR | gh | gh pr create --title "..." --body "..." --base main | | Review | Codex | codex review --base main "Review thoroughly" | | Comment | gh | gh pr comment --body "## Codex Review ..." | | Address | Claude Code | claude -p --dangerously-skip-permissions "Fix: ..." | | Commit | git | git commit -m "Address Codex review\n\nCodex recommended: ..." | | Merge | gh | gh pr merge --squash --delete-branch |