codex-usage

---

name: Codex Usage description: This skill should be used when the user asks to "use codex", "code generation", "code modification", "refactoring", or needs Codex MCP guidance. Provides Codex tool usage patterns and configuration. version: 0.2.0

Copy  Example:
  developer-instructions: "Follow TypeScript strict mode. Use functional components with hooks. Prefer named exports."
</example>

Copy  Keep tasks focused:
  - One function at a time
  - One file at a time
  - Clear, specific requirements
</example>

<decision_tree name="when_to_use_codex"> What type of operation is needed? Do NOT use Codex; use Explore agent or Serena Do NOT use Codex; use quality-assurance agent Do NOT use Codex; use security agent Do NOT use Codex; use test agent Do NOT use Codex; use docs agent Do NOT use Codex; use quality-assurance agent Use Codex with clear requirements Use Codex with context Use Codex after ensuring tests exist </decision_tree>

<decision_tree name="codex_vs_basic_tools"> Can basic tools (Read/Edit/Write) accomplish this? Use Edit tool Use Edit tool Use Write tool Use Codex Use Codex Use Codex </decision_tree>

<anti_patterns> Attempting to modify multiple files in single Codex call Make separate Codex calls for each file

<best_practices> Prefer basic tools (Read/Edit/Write) when sufficient One clear, small task per Codex call Separate phases: research -> design -> implementation No multi-file edits in single Codex call Provide context about existing code patterns Specify expected output format or structure Use codex-reply for iterative refinement </best_practices>

<error_escalation> Codex generates code with minor style differences Note in report, adjust style manually Codex output requires significant adjustments Use codex-reply for refinement or switch to Edit tool Codex fails to understand requirements STOP, break task into smaller pieces, rephrase requirements Codex generates potentially harmful code BLOCK operation, require explicit user review </error_escalation>

<related_skills> Alternative for code navigation and analysis; use for research tasks Fetch library documentation before code generation Shared enforcement and escalation patterns Task delegation patterns Ensure test coverage before refactoring Research methodology before implementation </related_skills>