← ClaudeAtlas

codex-review-gatelisted

Submit work to Codex for review and iterate until unconditional approval. Use after completing implementation tasks, before merging, or when a development process requires Codex sign-off.
verivus-oss/llm-cli-gateway · ★ 8 · AI & Automation · score 75
Install: claude install-skill verivus-oss/llm-cli-gateway
# Codex Review Gate Submit completed work to Codex via the llm-gateway for review. Iterate on feedback until you receive unconditional approval. This is the standard quality gate used across all VerivusAI projects. ## Dispatch Defaults Apply these on every dispatch unless the caller has explicitly overridden a rule in the current turn: 1. **Omit `model`** — let the gateway use its configured default per CLI. 2. **`approvalStrategy:"mcp_managed"`** is the skill dispatch default (the gateway schema default is `"legacy"`). For Codex, also pass `fullAuto:true`; this gives sandboxed autonomy while keeping the gateway approval gate in front of execution. 3. **No wallclock timeout; poll every 60 s** — `idleTimeoutMs` is a separate no-output safeguard. 4. **Iterate until unconditional APPROVED** (review dispatches only) — every review prompt must end with "End with APPROVED or NOT APPROVED with findings." Loop: dispatch → parse verdict → on `NOT APPROVED` or conditional, fix + re-submit → repeat. Escalate after 3 rounds. This rule does **not** apply to pure implementation or non-review analysis dispatches. ## When to Use - After completing an implementation task - Before merging or shipping - When CLAUDE.md or a development process mandates "Codex review via llm gateway" - When a plan says "iterate until unconditional approval" ## Protocol ### Step 1: Submit for Review Use `codex_request` with a review prompt that includes: - What was changed and why - File paths (let Codex