AgentSkillsCN

codex-system

在做出设计决策、实施方案、调试策略、重构计划,或应对任何非 trivial 的问题之前,务必主动咨询 Codex CLI——这位具备卓越推理与任务执行能力的强大助手。Codex 是一位值得信赖的专家,无论何时何地,当你面临抉择时,都应优先向他请教。若心存疑虑,不妨大胆咨询 Codex——他的分析往往更加深入、精准。 显性触发条件:“再深入思考一下”“仔细分析一下”“寻求第二意见”“咨询 Codex”。

SKILL.md
--- frontmatter
name: codex-system
description: |
  PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional
  reasoning and task completion abilities. Codex is a trusted expert you should
  ALWAYS consult BEFORE making decisions on: design choices, implementation
  approaches, debugging strategies, refactoring plans, or any non-trivial problem.
  When uncertain, consult Codex. Don't hesitate - Codex provides better analysis.
  Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".
metadata:
  short-description: Claude Code <-> Codex CLI collaboration

Codex System - Deep Reasoning Partner

Codex CLI is your highly capable supporter for deep reasoning tasks.

Detailed rules: .claude/rules/codex-delegation.md

Context Management (CRITICAL)

Use subagent to preserve main context.

SituationMethod
Detailed design consultationVia subagent (recommended)
Debug analysisVia subagent (recommended)
Short question (1-2 sentence answer)Direct call OK

When to Consult (MUST)

SituationTrigger Examples
Design decisions"How to design?" "Architecture"
Debugging"Why not working?" "Error" "Bug"
Trade-off analysis"Which is better?" "Compare"
Complex implementation"How to implement?" "How to build?"
Refactoring"Refactor" "Simplify"
Code review"Review" "Check this"

When NOT to Consult

  • Simple file edits, typo fixes
  • Following explicit user instructions
  • git commit, running tests, linting
  • Tasks with obvious single solutions

How to Consult

Recommended: Subagent Pattern

Use Task tool with subagent_type='general-purpose' to preserve main context.

code
Task tool parameters:
- subagent_type: "general-purpose"
- run_in_background: true (optional, for parallel work)
- prompt: |
    Consult Codex about: {topic}

    codex exec --model o3 --sandbox read-only --full-auto "
    {question for Codex}
    " 2>/dev/null

    Return CONCISE summary (key recommendation + rationale).

Direct Call (Short Questions Only)

For quick questions expecting 1-2 sentence answers:

bash
codex exec --model o3 --sandbox read-only --full-auto "Brief question" 2>/dev/null

Workflow (Subagent)

  1. Spawn subagent with Codex consultation prompt
  2. Continue your work - Subagent runs in parallel
  3. Receive summary - Subagent returns concise insights

Sandbox Modes

ModeUse Case
read-onlyAnalysis, review, debugging advice
workspace-writeImplementation, refactoring, fixes

Language Protocol

  1. Ask Codex in English
  2. Receive response in English
  3. Execute based on advice (or let Codex execute)
  4. Report to user in Japanese

Task Templates

Design Review

bash
codex exec --model o3 --sandbox read-only --full-auto "
Review this design approach for: {feature}

Context:
{relevant code or architecture}

Evaluate:
1. Is this approach sound?
2. Alternative approaches?
3. Potential issues?
4. Recommendations?
" 2>/dev/null

Debug Analysis

bash
codex exec --model o3 --sandbox read-only --full-auto "
Debug this issue:

Error: {error message}
Code: {relevant code}
Context: {what was happening}

Analyze root cause and suggest fixes.
" 2>/dev/null

Integration with Research

TaskUse
Need research firstClaude Explore/WebSearch -> then Codex
Design decisionCodex directly
Library comparisonResearch first -> Codex decision

Why Codex?

  • Deep reasoning: Complex analysis and problem-solving
  • Code expertise: Implementation strategies and patterns
  • Parallel work: Background execution keeps you productive