Understand Explain

This is for when you're staring at unfamiliar code and need more than a quick summary. It walks through the knowledge graph to find your target file or function, maps out what calls it and what it depends on, figures out which architectural layer it lives in, then reads the actual source and explains it all in context. The approach is methodical: grep first, read strategically, never dump the whole graph into context. What I like here is that it doesn't just explain the code in isolation. It shows you the neighborhood, the data flow, the why-it-exists. Good for onboarding or diving into a gnarly module you need to modify but don't yet understand.

skills.sh installs: 4.2K
GitHub stars: 91.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add egonex-ai/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[]}