route-codex-review
Skill10 starsChanged 27 days agoMITView on GitHub
Forced adversarial review pre-delivery — hands Claude-generated code, content, or plans to Codex (GPT-5.5) to find bugs, security risks, missing tests, and missed edge cases. Trigger when the user says "review the code you wrote", "check your work", "second opinion", "sanity-check what you wrote", "adversarial review", or before client-bound delivery of substantial Claude output.
In this repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- blast-promptSkill
- client-outreachSkill
- content-draftSkill
- copywritingSkill
- csv-to-reportSkill
- design-accessibilitySkill
- design-buildSkill
- design-croSkill
- design-dimensionsSkill
- design-motionSkill
- design-researchSkill
- design-system-genSkill
- design-system-persistSkill
- design-tokens-emitSkill
- design-visual-qaSkill
- html-extractSkill
- parallel-buildSkill
- portable-html-portSkill
- qa-gateSkill
- route-gemini-contextSkill
- route-three-brainSkill
- seo-auditSkill
- seo-backlinksSkill
- seo-clusterSkill
- seo-competitor-pagesSkill
- seo-content-briefSkill
- seo-contentSkill
- seo-dataforseoSkill
- seo-driftSkill
- seo-ecommerceSkill
- seo-firecrawlSkill
- seo-geoSkill
- seo-googleSkill
- seo-hreflangSkill
- seo-image-auditSkill
- seo-image-genSkill
- seo-local-unifiedSkill
- seo-pageSkill
- seo-programmaticSkill
- seo-schemaSkill
- seo-sitemapSkill
- seo-strategySkill
- seo-sxoSkill
- seo-technicalSkill
The file
Files
route-codex-review
Family: routing Status: Stable
Purpose
The execution arm of the no-self-review rule. Hands Claude's output to Codex for an independent, adversarial pass — bugs, security risks, missing edge cases/tests, broken invariants, unclear logic. Mandatory for substantial output heading to a client or production, or whenever the user asks to verify Claude's work.
Triggers
- "review the code you wrote" / "review what you just did"
- "check your work" / "look over what you wrote" / "give it a once-over"
- "second opinion" / "sanity-check what you wrote" / "double-check this"
- "adversarial review" / "have codex review" / "is this right"
Scoped to Claude's own output. Bare "audit this" / "audit my site" belongs to the SEO/QA families, not here (see
references/ENGINE-CONTRACTS.md§3).
Inputs
- The output to review (diff, files, content, or plan)
- Review focus (bugs / security / correctness / completeness / all)
Steps
- Check Codex is available:
codex --version. If absent, tell the user it's off until installed and offer a structured manual review from a different lens (never a same-model self-review). - Bundle the context — the diff or the specific files, plus what was tried and the relevant constraints.
- Invoke Codex:
For untracked code, pipe the file(s) instead ofgit diff | codex exec --skip-git-repo-check "Review this diff. Find bugs, security risks, missing tests, edge cases. Be specific and adversarial."git diff. For a harder pass:...codex exec ... "Adversarial review. Challenge the design. Prove what's broken." - Parse Codex's findings into severity-tagged items (Critical → nits).
- Integrate, don't rubber-stamp. For each finding decide fix / defer / dismiss (with a reason). Apply the fixes, then re-verify.
Outputs
- A severity-tagged findings list from Codex
- The integrated outcome: what was fixed, deferred, or dismissed (with reasons)
Dependencies
- The
codexCLI (or the adjacentopenai-codextool) (optional — adds an independent GPT-5.5 adversarial pass; free path: a structured manual review from a different lens, never a same-model self-review).
Notes
Claude reviewing its own substantive output repeats its own blind spots; this skill operationalizes routing that review to a different model before it ships.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

