ask-codex
Skill248 starsChanged 3 months agoMITView on GitHub
Ask OpenAI Codex (GPT-5) a one-off question about the current repo and get its answer back, without spinning up a subagent. Use when the user says "ask codex", "what does GPT think", "get a second opinion on this", or when you want an independent read on a design call, a tricky bug, or an unfamiliar area of the codebase.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- maxatwork/skillstheir own version, first seen Nov 8, 2026
- finalize/skillstheir own version, first seen Nov 1, 2026
- madeordinary/serel-memorytheir own version, first seen Nov 1, 2026
- PolyArch/humanizetheir own version, first seen Oct 8, 2026
- BackToCimaCoppi/Praxistheir own version, first seen Sep 23, 2026
- Yumeno/add_codexclitheir own version, first seen Sep 19, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- PolyArch/humanize★ 1.5ksame name
- bookSiYi1412/ask-codex★ 9same name
- s977043/river-review★ 7same name
- BackToCimaCoppi/Praxis★ 6same name
- yeaight7/agent-powerups★ 6same name
- WebisityStudio/claude-codex-mcp-bridge★ 2same name
- madeordinary/serel-memory★ 1same name
- finalize/skills★ 0same name
- maxatwork/skills★ 0same name
- Yumeno/add_codexcli★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- asset-setSkill
- codex-delegateSkill
- codex-reviewSkill
- edit-imageSkill
- generate-imageSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
Use -r for a genuine follow-up — it keeps Codex's own context and avoids paying to re-read the repo:
- Distinctive: line 56
Verify any specific claim against the repo before acting on it.
- Very specific: line 57
Read-only unless told otherwise: Don't pass -s workspace-write on your own initiative.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ask Codex a question
For a single question with a single answer. Anything multi-step or long-running
belongs to a subagent (codex-second-opinion, codex-reviewer, codex-debugger).
codex-run -C <repo-dir> "<self-contained question>"codex-run prints only Codex's final answer on stdout (it captures the final
message via codex exec -o rather than dumping the whole event log). It defaults
to a read-only sandbox, so Codex can read the repo but cannot change anything.
Writing the question
Codex has zero knowledge of this conversation. Every question must stand alone:
- Name the files or directories it should look at.
- State what you already know or already tried.
- Say what shape of answer you want ("name the single most likely cause and the line to look at", "answer yes/no then justify in three sentences").
codex-run -C /path/to/repo \
"In src/auth/session.ts, refreshToken() occasionally returns a token that fails validation immediately. I suspect a clock-skew issue in the exp comparison. Read that file plus src/auth/jwt.ts and tell me the single most likely root cause and the exact line. Be concise."Useful options
-s workspace-write let Codex modify files (only when the user asked for that)
-m gpt-5-codex model override
-r continue the previous codex session (follow-up question)
--timeout 1800 raise the 900s default for a big repo sweep
--raw also print Codex's full event log to stderr, for debuggingUse -r for a genuine follow-up — it keeps Codex's own context and avoids paying
to re-read the repo:
codex-run -C /path/to/repo -r "Now show me the minimal patch for that."Rules
- Bash timeout ≥ 600000 ms (10 min) — Codex explores the repo before answering.
- Report its answer as Codex's, not as your own conclusion. Quote it, then add your own take separately if you disagree — the value here is having two independent opinions, and blending them destroys that.
- Sanity-check it. Codex can confidently cite files or lines that don't exist. Verify any specific claim against the repo before acting on it.
- Read-only unless told otherwise. Don't pass
-s workspace-writeon your own initiative. - Each call spends the user's ChatGPT plan quota. One question, one call.
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.