codex-loop
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR
Install / Use
npx skills add oliver-kriska/claude-elixir-phoenix --skill codex-loopInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of codex-loop
codex-loop scores 82/100 on our quality scale, 3309th of 4,613 Development & Engineering skills we index.
Its SKILL.md is 5.0 KB long, well organised into 11 sections with 3 code examples: a solid amount of guidance for an agent.
It has 560 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 3 days ago, so codex-loop is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
codex-loop compared with similar skills
All 4 of these similar skills score higher than codex-loop; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| codex-loop (this skill)by oliver-kriska | 82 | 560 | 3d ago | SKILL.md |
| ai-job-searchby MadsLorentzen | 100 | 45.0k | 2d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 41.8k | 5d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 13d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 13d ago | SKILL.md |
Frequently asked questions
- How do I install codex-loop?
- Run
npx skills add oliver-kriska/claude-elixir-phoenix --skill codex-loop. The install tabs above show the steps for each supported agent. - Which AI agents does codex-loop work with?
- It is written for Claude Code and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is codex-loop safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is codex-loop still maintained?
- The repository was last updated 3 days ago, so codex-loop is actively maintained.
Skill content
View source on GitHubname: codex-loop description: Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing. effort: medium argument-hint: "[--base <branch>] [--uncommitted] [--auto] [--max-rounds N]"
Codex Loop (fix until clean)
Critic→Refiner loop with the Codex CLI as external critic: review → fix
approved findings → verify → re-review, until codex is clean or rounds run
out. Codex reviews; Claude fixes. Complements /phx:review (Claude panel)
— run either or both before a PR.
Usage
/phx:codex-loop # diff vs default branch, interactive
/phx:codex-loop --uncommitted # staged + unstaged + untracked
/phx:codex-loop --base develop # explicit base branch
/phx:codex-loop --auto # auto-approve P0/P1/P2, skip P3
/phx:codex-loop --max-rounds 2 # default 3
Iron Laws
- BOUNDED rounds — never exceed --max-rounds (default 3) — each round costs codex quota; report remaining findings instead of looping on
- Verify BEFORE re-review —
mix compile --warnings-as-errors+ tests must pass before burning a codex round on broken code - NEVER commit or push — leave git to the user
- Codex findings get Iron Law scrutiny — decline suggestions that violate an Iron Law, with explanation in the round report
- Skipped findings are reported, never dropped — every finding ends as fixed, declined (with reason), or deferred-by-user
- Missing CLI stops the skill with an install hint — suggest
/phx:reviewas the codex-free alternative; never crash
Workflow
Step 1: Preflight
Run command -v codex. If missing: STOP.
Show the install hint (brew install codex or npm i -g @openai/codex,
then codex login; codex doctor to diagnose) and suggest /phx:review.
Then two cheap checks that save review rounds:
- Dirty tree (
git status --short, only when using--base): codex inspects working-tree state too and WILL flag local dirt (stray edits, dirty submodules) as findings. Surface the dirt and ask: clean/stash first, or proceed knowing round 1 may spend findings on it. - Missing rubric: if
AGENTS.mdhas no## Review guidelinessection, note once that/phx:initinstalls the Elixir rubric that steers codex priorities — then proceed (it works without, on defaults).
Step 2: Detect Diff Mode
- Flag passed (
--base/--uncommitted) → use as given - Commits ahead of the default branch →
--base {default} - No commits yet →
--uncommitted
Step 3: Round Loop (max --max-rounds, default 3)
-
Review — ONE foreground Bash call, explicit
timeout: 600000(large diffs run 10+ min). On timeout with the process alive: ONEuntil [ -f {out} ]; do sleep 5; donewait — never poll-spam orpkilla running review (quota is spent either way). ALWAYS silence the streams — only the-ofile matters (10k+ lines otherwise):codex exec review --base {branch} --ephemeral \ -o /tmp/codex-round-{n}.md > /tmp/codex-round-{n}.log 2>&1NEVER pass custom instructions with a diff-mode flag — the CLI rejects the combination; the rubric comes from AGENTS.md
## Review guidelines(/phx:init). Parse the output file, NOT the exit code (0 even with findings). Recipes:${CLAUDE_SKILL_DIR}/references/codex-cli.md. -
Clean check — parse the output file; no
- [P{n}]bullets means CLEAN → go to Step 4. -
Triage — emit the findings table (
# | P | file:line | title | proposed action) as visible response text BEFORE anyAskUserQuestioncall — a table composed only in thinking never renders. Then ask approve-or-skip per finding (AskUserQuestion). With--auto: approve P0/P1/P2, skip P3 (list skipped in the round report). -
Fix — apply approved fixes with user-visible diffs. Check each against Iron Laws first (Law 4).
-
Verify — scoped, before the next round:
mix format {changed_files} && \ mix compile --warnings-as-errors && mix test {affected_tests}If verification fails 3 times, STOP with a BLOCKER report — do not burn another codex round on broken code.
-
Next round (n+1).
Step 4: Final Report
## Codex Loop Report — {CLEAN | MAX ROUNDS REACHED | BLOCKED}
Rounds: {n}/{max} | Fixed: {n} | Declined (Iron Law): {n} | Deferred: {n}
{per-round: findings → outcome}
{remaining findings if not CLEAN}
On CLEAN: suggest /phx:compound for non-obvious fixes, then commit/PR.
On MAX ROUNDS: list remaining findings; offer /phx:plan to convert them
into a follow-up plan.
Integration
implement → /phx:codex-loop (YOU ARE HERE) → clean → commit/PR → /phx:watch-pr --codex
↑ or arrive from /phx:review --codex verdict REQUIRES CHANGES
References
${CLAUDE_SKILL_DIR}/references/codex-cli.md— invocation recipes, parse patterns, verified gotchas (CLI 0.142.5)
Related Skills
ai-job-search
45.0kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
41.8kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
