Programming · Learning & explanation
understand-explain
/understand-explain
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
For whom
- Author
- garr1k ↗
- Repository
- understand-anything ↗
- Licence
- MIT
- Last repository change
- 16.06.2026
Assessment and security
90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 16.06.2026, without references to retired models or APIs.
Licence
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
Arguments
/understand-explain [file-path]
Original author description
Use when you need a deep-dive explanation of a specific file, function, or module in the codebase
How it works
- Graph Structure Reference
- How to Read Efficiently
- Instructions
Original SKILL.md headings · 54 lines, 471 words
SKILL.md preview
---
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]
---
# /understand-explain
Provide a thorough, in-depth explanation of a specific code component.
## Graph Structure Reference
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?}
- Code node types: file, function, class, module, concept
- Non-code node types: config, document, service, table, endpoint, pipeline, schema, resource
- Domain/knowledge node types: domain, flow, step, article, entity, topic, claim, source
- IDs use the node type as prefix, e.g. `file:path`, `function:path:name`, `config:path`, `article:path`
- `edges[]` — each has {source, target, type, direction, weight}
- Key types: imports, contains, calls, depends_on, configures, documents, deploys, triggers, contains_flow, flow_step, related, cites
- `layers[]` — each has {id, name, description, nodeIds[]}
- `tour[]` — each has {order, title, description, nodeIds[]}
## How to Read Efficiently
1. Use Grep to search within the JSON for relevant entries BEFORE reading the full file
2. Only read sections you need — don't dump the entire graph into context
3. Node names and summaries are the most useful fields for understanding
4. Edges tell you how components connect — follow imports and calls for dependency chains
## Instructions
1. Check that `.understand-anything/knowledge-graph.json` exists. If not, tell the user to run `/understand` first.
2. **Find the target node** — use Grep to search the knowledge graph for the component: "$ARGUMENTS"
- For file paths (e.g., `src/auth/login.ts`): search for `"filePath"` matches
- For function notation (e.g., `src/auth/login.ts:verifyToken`): search for the function name in `"name"` fields filtered by the file path
- Note the exact node `id`, `type`, `summary`, `tags`, and `complexity`
3. **Find 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)
- Note the connected node IDs and edge types
4. **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.
5. **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.
6. **Read the actual source file** — Read the source file at the node's `filePath` for the deep-dive analysis.
7. **Explain the component in context**:
- Its role in the architecture (which layer, why it exists)
- Internal structure (functions, classes it contains — from `contains` edges)
- External connections (what it imports, what calls it, what it depends on — from edges)
- Data flow (inputs → processing → outputs — from source code)
- Explain clearly, assuming the reader may not know the programming language
- Highlight any patterns, idioms, or complexity worth understanding
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · garr1k/understand-anything | 90 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| Egonex-AI/Understand-Anything | 100 | MIT |
Database snapshot: 13.11.2026 · package version 89d395043a0f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 84analyze-code
Comprehensive code explanation and analysis. Use when user says "explain this file to me", "what does this code do", "analyze the security of this module", "review the performance of this function", or "help me understand this architecture". - 90explain-code
Explain how a piece of code works (a function, file, module, or a flow like "what happens when a user signs up") with file and line references, traced from the actual code. Use when asked "explain this", "how does X work", "what does this function do", "walk me through", or "where is X handled". - 100code-explanation
Explains complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Use when user asks to explain code, understand algorithms, analyze design patterns, wants code walkthroughs, or mentions "explain this code", "how does this work", "code breakdown", or… - 100explain
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where… - 100trove-explain
Explain code, architecture, or data flow at the appropriate level for the audience. Use when someone needs to understand unfamiliar code, a module, or system design. - 90understand-chat
Use when you need to ask questions about a codebase or understand code using a knowledge graph