Menu
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | understand-explain |
| description | Use when you need a deep-dive explanation of a specific file, function, or module in the codebase |
| argument-hint | ["file-path"] |
Provide a thorough, in-depth explanation of a specific code component.
The knowledge graph JSON has this structure:
project — {name, description, languages, frameworks, analyzedAt, gitCommitHash}nodes[] — each has {id, type, name, filePath?, summary, tags[], complexity, languageNotes?}
file:path, function:path:name, config:path, article:pathedges[] — each has {source, target, type, direction, weight}
layers[] — each has {id, name, description, nodeIds[]}tour[] — each has {order, title, description, nodeIds[]}Check that .understand-anything/knowledge-graph.json exists. If not, tell the user to run /understand first.
Find the target node — use Grep to search the knowledge graph for the component: "$ARGUMENTS"
src/auth/login.ts): search for "filePath" matchessrc/auth/login.ts:verifyToken): search for the function name in "name" fields filtered by the file pathid, type, summary, tags, and complexityFind all connected edges — Grep for the target node's ID in the edges section:
"source" matches → things this node calls/imports/depends on (outgoing)"target" matches → things that call/import/depend on this node (incoming)Read connected nodes — for each connected node ID from step 3, Grep for those IDs in the nodes section to get their name, summary, and type. This builds the component's neighborhood.
Identify the layer — Grep for the target node's ID in the "layers" section to find which architectural layer it belongs to and that layer's description.
Read the actual source file — Read the source file at the node's filePath for the deep-dive analysis.
Explain the component in context:
contains edges)Throwaway HTML mockups: 2-3 design variants to compare.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
Execute implementation plans by dispatching fresh subagents per task with two-stage review. Use when executing a multi-task implementation plan, when context is getting too long for quality output, or when you want maximum isolation between tasks.
Core tGD rules that MUST be followed at all times — the Verification Iron Law, per-phase tone, the Command Closing Report, and human sign-off. Load this at the start of every tGD session (the session-start meta-skill tgd-router points here) and whenever a command references it. Do not skip, do not rationalize exceptions.
Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.