codex-iterative
Skill18 starsChanged 6 months agoNo licenceView on GitHub
Multi-round iterative review via Codex CLI with session resumption — Codex reviews a plan, design, or diff, returns a verdict (APPROVED/REVISE), and Claude fixes issues and resubmits until Codex approves. Codex remembers all prior feedback across rounds via session resume, so it verifies fixes rather than re-discovering the same issues. MUST use this skill when the user wants Codex to review a plan, design doc, architecture proposal, or diff iteratively with multiple rounds of feedback. Trigger phrases include "codex iterative review", "iterative review", "review my plan with codex", "have codex review this iteratively", "multi-round review", "review until approved", "get codex to tear it apart", "codex review and verify fixes", "not just a single pass", "keep reviewing until it's solid", or "/codex-iterative". Also trigger when the user asks for a Codex review where they want verification that fixes address prior feedback, session persistence across review rounds, or accumulated context. Do NOT trigger for quick one-shot codex reviews (/codex), deep code audits (/codex-audit), codex delegation for non-review tasks, or when the user explicitly says they want a single pass.
In this repository9 other files it gives its agents.
- codex-auditSkill
- codexSkill
- coding-guidelinesSkill
- final-reviewSkill
- grill-meSkill
- node-walkthroughSkill
- orchestrate-laneSkill
- parallel-subagentsSkill
- techdebtSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.