Understand Explain

This is for when you need to actually understand a piece of code, not just skim it. Point it at a file, function, or module and it walks through the knowledge graph to map out what the component does, what depends on it, what it depends on, and where it fits in your architecture. It greps the graph strategically instead of dumping everything into context, then reads the actual source for a full explanation. The output assumes you might not know the language well, which is honestly useful even when you do. Works best after you've run the base understand command to generate the knowledge graph. Good for onboarding, refactoring decisions, or those moments when you inherit something gnarly and need the full picture.

skills.sh installs: 1.2K
GitHub stars: 73.8K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add lum1104/understand-anything --skill understand-explain --agent claude-code

Installs into .claude/skills of the current project.

Files

/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[]}