codex-explain
Codex Explain Skill
Trigger
- Keywords: explain code, what does this do, how does this work, code walkthrough
When NOT to Use
- Code review (use
codex-code-review) - Bug investigation (use
bug-fixorissue-analyze) - Architecture overview (use
code-explore)
Workflow
Read target → [Collect context] → Codex explain → Output explanation
Step 1: Read Target File
Read file content. If --lines specified, extract only that range.
Step 2: Codex Explanation
Use mcp__codex__codex with explanation prompt. See references/codex-prompt-explain.md.
Config: sandbox: 'read-only', approval-policy: 'never'
Depth Levels
| Level | Description |
|---|---|
| brief | One-sentence summary |
| normal | Functional overview + execution flow + key concepts (default) |
| deep | + Design patterns + complexity + issues + dependencies |
Output
## Code Explanation: <target>
- **Depth**: brief / normal / deep
- **Summary**: <functional overview>
- **Execution flow**: <key paths>
- **Key concepts**: <patterns, abstractions>
Verification
- Codex independently researched project context (imports, callers)
- Explanation matches requested depth level
- Key concepts are identified and explained
References
- Explanation prompt:
references/codex-prompt-explain.md
Examples
Input: /codex-explain src/service/order/order.service.ts
Action: Read file → Codex explain (normal) → Functional summary + detailed explanation
Input: /codex-explain src/service/xxx.ts --depth deep
Action: Read file → Codex explain (deep) → Patterns + complexity + issues
Input: /codex-explain src/xxx.ts --lines 50-100
Action: Read lines 50-100 → Codex explain → Focused explanation
More from sd0xdev/sd0x-dev-flow
statusline-config
Customize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color scheme', wants to add/remove/change segments (cost, git, model, context), switch color themes (catppuccin, dracula, nord), or asks what can be shown in the statusline.
52tech-spec
Tech spec generation and review. Use when: designing features, writing specs, spec review. Not for: requirements analysis (use req-analyze), implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document.
45codex-brainstorm
Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.
7security-review
Security review via Codex MCP. Use when: OWASP Top 10 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
7test-review
Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
7post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
6