Menu
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 with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | codex |
| description | Use OpenAI Codex CLI for complex debugging, code analysis, or when stuck on difficult problems. Invokes Codex with a file-based question/answer pattern. |
| disable-model-invocation | true |
When you encounter a difficult problem that would benefit from a second perspective or deep analysis, use Codex via the file-based pattern.
Write to /tmp/question.txt with:
Example structure:
I have a [component] that fails with [specific error].
Here is the full function:
[paste complete code]
Key observations:
1. [What works]
2. [What fails]
3. [When it fails]
Can you identify:
1. [Specific question 1]
2. [Specific question 2]
Please write a detailed analysis to /tmp/reply.txt
cat /tmp/question.txt | codex exec --full-auto
Flags:
exec: Non-interactive execution mode (required for CLI use)--full-auto: Run autonomously without promptsDo 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...").
Read /tmp/reply.txt and evaluate suggestions critically. Codex may identify real bugs but can occasionally misinterpret specifications.
codex exec not bare codex-o flag has a valid path--full-auto avoids blocking promptsFor shorter questions:
echo "Explain the JPEG progressive AC refinement algorithm" | codex exec --full-auto
But for debugging, the file-based pattern is better for refining questions and keeping records.
DDD planning and review workflow for greenfield systems and brownfield codebases. Use when shaping bounded contexts, ubiquitous language, aggregates, invariants, integration boundaries, or reviewing an existing model for DDD fit.
Copy the skills collection from /Users/shrivatsa/Documents/dev-setup/skills into the current repository, another repository, or an explicit skills directory. Use when the user asks to copy, sync, install, update, or bring over their dev-setup skills.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Expert HIPAA compliance assistant for healthcare and software contexts. Use this skill whenever the user mentions HIPAA, PHI (Protected Health Information), ePHI, covered entities, business associates, healthcare data privacy, medical records, health information security, BAA (Business Associate Agreements), or any compliance review involving patient data. Also trigger for requests to draft privacy notices, HIPAA policies, consent forms, security risk assessments, or breach notification letters. Use for developers building healthcare software who need technical safeguard guidance (encryption, access controls, audit logs), compliance officers reviewing documents or procedures, and anyone asking "is this HIPAA compliant?" or "what does HIPAA require for X?". When in doubt about whether a healthcare or data privacy question falls under this skill — use it.
Outcome-first architecture discovery and recommendation skill. Use when you need to iteratively clarify requirements, ask leading questions about business goals and constraints, maintain a running intake file so users do not repeat themselves, and produce a sharp architecture recommendation with tradeoffs and risks.
Add, remove, or refine research fields for an existing research outline, with concise evidence-first output.