agentleFS
Sign inStart free
sd0xdevsd0xdev/sd0x-dev-flow/skills/codex-explain/SKILL.md

codex-explain

Skill192 starsChanged 36 days agoMITView on GitHub

Explain complex code via Codex exec. 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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read file content. If --lines specified, extract only that range.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-fix or issue-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

Dispatch per @skills/codex-code-review/references/codex-transport.md § Start with the explanation prompt. See references/codex-prompt-explain.md.

Depth Levels

LevelDescription
briefOne-sentence summary
normalFunctional 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free