Ask Codex

TRIGGER when: user requests implementation work, repo exploration, data/log inspection, broad codebase search, impact analysis, verification-heavy shell work, or explicitly mentions Codex ("用 codex 做", "让 codex 执行", "ask codex to...", "use codex", "delegate to codex"). Also trigger for heavy internal subtasks that Claude Code might otherwise offload to a lightweight model/Haiku. DO NOT TRIGGER when the task is primarily user-facing product judgment, architecture choice, git/PR/release operations, or requires multi-turn clarification before useful work can begin. This skill routes work between

10 starsSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add bookSiYi1412/ask-codex --skill ask-codex

Manual install

git clone --depth 1 https://github.com/bookSiYi1412/ask-codex.git /tmp/ask-codex
mkdir -p ~/.claude/skills
cp -r /tmp/ask-codex/. ~/.claude/skills/ask-codex

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Claude Code × Codex Collaboration Framework

Claude Code is the architect and coordinator; Codex is the autonomous implementer.

**Core principle:** Claude Code handles user interaction, scope control, product/architecture decisions, and final verification. Codex handles heavyweight codebase exploration, data inspection, implementation, and command execution. Default to Codex for repo-bound heavy lifting; keep Claude Code focused on judgment and synthesis. For anything that benefits from ongoing observation or mid-course correction, use the brokered session flow instead of one-shot execution.

## Iron Laws

1. **Route first** — On receiving an implementation task, determine routing (self vs delegate vs split) before acting.
2. **Review loop** — Every Codex output must be verified by Claude Code (at minimum: read changed files). Never blindly trust results.
3. **Self-contained context** — Prompts sent to Codex must be fully self-contained. Never rely on "it should know."
4. **Prefer session reuse** — When corrections are needed, prefer `--session` to continue in the original session rather than starting fresh and losing context.
5. **Never hide failures** — When Codex fails, report honestly to the user with failure analysis. No silent retries.
6. **Auto-offload heavy lifting** — If a subtask is mostly repo/data exploration or verification work, prefer Codex by default instead of Claude Code or an internal lightweight/Haiku-style handoff.

## Critical Rules

Read the full skill on GitHub

Details

Skill name: ask-codex
Repository: bookSiYi1412/ask-codex
License: Apache-2.0
Repo updated: 23 April 2026

FAQ

What does the Ask Codex skill do?

How do I install the Ask Codex skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add bookSiYi1412/ask-codex --skill ask-codex. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ask Codex popular?

It lives in bookSiYi1412/ask-codex, which has 10 GitHub stars and 0 forks.

Related skills

Codewiki

ekuttan/codewiki

Generate a structured product knowledge base from codebase scanning. Creates a codewiki/ folder with architecture docs, user flows, API reference, service maps, and more. Also generates CLAUDE.md. Handles single repos, monorepos, and multi-repo microservices. Use when asked to document a project, generate a knowledge base, map architecture, create onboarding docs, or set up CLAUDE.md for a codebase.

Software Development

Thermo Nuclear Code Quality Review

Oreo992/thermo-nuclear-code-quality-review

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

Software Development

Coding Workflow

w93139/coding-workflow

Guide implementation, bug fixes, scripts, and small projects through a proportionate brief, scoped changes, fresh verification, and independent read-only review. Use when Codex is asked to change code; keep tiny edits lightweight and do not activate for explanation-only or review-only requests.

Software Development

Session Wrap

leonsong09/session-wrap

Use when the user wants to wrap up the current coding session, summarize the current session before ending work, document learnings, decide what to commit, or says 总结会话, 会话总结, 收尾, 会话收尾, 结束会话, 总结本次会话.

Software Development

Ip Studio

CheshireMew/ip-studio

创建、锁定并长期复用个人或品牌 IP 角色，并用同一角色实际制作头像、主页横幅、资料卡、文章视觉、离散状态式 2D 动态角色素材和 Codex v2 桌宠；环境没有生图能力时才回退为完整提示词包。Use when a user wants to turn identity cues or existing art into a stable stylized character kit; use that locked character in social or content visuals; produce runtime-grounded static poses, directional clips, state loops, one-shot actions, transitions, sprite atlases, or interface-character motion; or build a Codex-compatible v2 pet as one fixed platform adapter. Do not use for generic visuals without an IP character, photorealistic digital doubles, general motion graphics, skeletal animation,

Software Development

Project Daily Summary

leonsong09/project-daily-summary

Use when the user wants a same-day Codex work summary grouped by project folder or repository, combining today's Codex sessions, extracted plans, completed items, commits, and uncommitted changes, or says 项目日报, 日报, 今日工作总结, 按项目总结今天, 总结今天所有 Codex 会话, 总结今天会话+提交+未提交改动.

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.