sd0xdev/codex-explain
skills/codex-explain/SKILL.md
Explain complex code via Codex MCP. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth.
$ install --global
skillsauthnpx skillsauth add sd0xdev/sd0x-dev-flow codex-explainInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 9:04 PM1.8s1 file scanned
SKILL.md
- name:
- codex-explain
- description:
- Explain complex code via Codex MCP. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth.
- allowed-tools:
- mcp__codex__codex, mcp__codex__codex-reply, Read, Grep, Glob
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
Related Skills
sd0xdev/zh-tw
documentation
VerifiedTrustedCommunity
Rewrite the previous reply in Traditional Chinese
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/watch-ci
development
VerifiedTrustedCommunity
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/verify
development
VerifiedTrustedCommunity
Verification loop — lint -> typecheck -> unit -> integration -> e2e
147SKILL.mdUpdated Apr 28, 2026
sd0xdev/update-docs
development
VerifiedTrustedCommunity
Research current code state then update corresponding docs, ensuring docs stay in sync with code.
147SKILL.mdUpdated Apr 28, 2026