shrivatsas/dev-setup/codex
Claude Code and agent skill by shrivatsas/dev-setup
- community
Checking that the SKILL.md file is still in the repository.
Use OpenAI Codex CLI for complex debugging, code analysis, or when stuck on difficult problems. Invokes Codex with a file-based question/answer pattern.
Install
npx vskill@latest install shrivatsas/dev-setup/codexSKILL.md
The same SKILL.md was published earlier as shrivatsas/dev-setup/codex.
Using Codex for Complex Debugging
When you encounter a difficult problem that would benefit from a second perspective or deep analysis, use Codex via the file-based pattern.
When to Use
- Debugging subtle bugs (bitstream alignment, off-by-one errors)
- Analyzing complex algorithms against specifications
- Getting detailed code review with specific bug identification
- Understanding obscure file formats or protocols
- When you've tried multiple approaches and are stuck
The Pattern
Step 1: Create a Question File
Write to /tmp/question.txt with:
- Clear problem statement
- The specific error or symptom
- The relevant code (full functions, not snippets)
- What you've already tried
- Specific questions you want answered
- Request: "Please write a detailed analysis to /tmp/reply.txt"
Example structure:
Step 2: Invoke Codex
Flags:
exec: Non-interactive execution mode (required for CLI use)--full-auto: Run autonomously without prompts
Do NOT use the -o flag. The prompt already instructs Codex to write its analysis to /tmp/reply.txt via its own shell commands. Using -o /tmp/reply.txt would overwrite the actual analysis with Codex's conversational stdout (e.g. "Wrote the analysis...").
Step 3: Read the Reply
Read /tmp/reply.txt and evaluate suggestions critically. Codex may identify real bugs but can occasionally misinterpret specifications.
Tips
- Provide complete code: Don't truncate functions. Codex needs full context.
- Be specific: "Why does Huffman decoding fail after 1477 blocks?" > "Why does this fail?"
- Include the spec: Mention relevant spec sections if debugging against a standard.
- Verify suggestions: Codex is helpful but not infallible. Always verify against authoritative sources.
- Iterate if needed: Create a new question.txt with additional context if first response doesn't solve the problem.
Common Issues
- "stdin is not a terminal": Use
codex execnot barecodex - No output: Check that
-oflag has a valid path - Timeout: Complex questions take time;
--full-autoavoids blocking prompts
Quick Alternative
For shorter questions:
But for debugging, the file-based pattern is better for refining questions and keeping records.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/codex/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/shrivatsas/dev-setup/codex)