v2.9.8

understand-chat

egonex-ai@egonex-ai⭐ 92.4k stars· last commit 4d ago· 134 open issues

Use when you need to ask questions about a codebase or understand code using a knowledge graph

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

7.0/10
Verified
Oct 8, 2026

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 92.4k on GitHubGitHub ↗

Very popular

🟢ProSkills ScoreAI Verified
7.0/10
📍

Not yet listed on ClawHub or SkillsMP

// README


You just joined a new team. The codebase is 200,000 lines of code. Where do you even start?

Understand Anything is a Claude Code Plugin that analyzes your project with a multi-agent pipeline, builds a knowledge graph of every file, function, class, and dependency, then gives you an interactive dashboard to explore it all visually. Stop reading code blind. Start seeing the big picture.

The goal isn't a graph that wows you with how complex your codebase is — it's a graph that quietly teaches you how every piece fits together.


✨ Features

[!NOTE] Want to skip the reading? Try the live demo in our homepage — a fully interactive dashboard you can pan, zoom, search, and explore right in your browser.

Explore the structural graph

Navigate your codebase as an interactive knowledge graph — every file, function, and class is a node you can click, search, and explore. Select any node to see plain-English summaries, relationships, and guided tours.

Understand business logic

Switch to the domain view and see how your code maps to real business processes — domains, flows, and steps laid out as a horizontal graph.

Analyze knowledge bases

Point /understand-knowledge at a Karpathy-pattern LLM wiki and get a force-directed knowledge graph with community clustering. The deterministic parser extracts wikilinks and categories from index.md, then LLM agents discover implicit relationships, extract entities, and surface claims — turning your wiki into a navigable graph of interconnected ideas.


🚀 Quick Start

1. Install the plugin

/plugin marketplace add Egonex-AI/Understand-Anything
/plugin install understand-anything

Using a local model? For privacy or enterprise setups, point your platform at a local model provider such as Ollama — follow their integration guide to change the model provider.

2. Analyze your codebase

/understand

A multi-agent pipeline scans your project, extracts every file, function, class, and dependency, then builds a knowledge graph saved to .ua/knowledge-graph.json. (Projects that already have a .understand-anything/ directory keep using it — it stays the data directory when present, so nothing needs migrating.)

Heads up on token usage: The initial /understand analyzes your whole codebase and can consume a significant number of tokens on large projects. We recommend running it on a token plan / subscription, or using a local model (see above) for initialization. Subsequent runs are incremental by default — only changed files are re-analyzed — so they use far fewer tokens.

Localized output: Use --language to generate content in your preferred language:

# Generate Chinese content (知识图节点描述和 Dashboard UI)
/understand --language zh

# Supported languages: en (default), zh, zh-TW, ja, ko, ru, vi

On the first run in a project — when you don't pass --language and no language is stored yet — /understand detects the language you're conversing in. If it isn't English, it asks you to confirm (or override) before generating; English conversations are unaffected. Your choice is saved to .ua/config.json and reused on every later run.

The --language parameter affects:

  • Node summaries and descriptions in the knowledge graph
  • Dashboard UI labels, buttons, and tooltips
  • Guided tour explanations

3. Explore the d

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • understand-anything-plugin/skills/understand-chat/SKILL.md4.7 KBupstream ↗
    ---
    name: understand-chat
    description: Use when you need to ask questions about a codebase or understand code using a knowledge graph
    argument-hint: "[query]"
    ---
    
    # /understand-chat
    
    Answer questions about this codebase using the knowledge graph in the project's data directory (`.ua/knowledge-graph.json`, or the legacy `.understand-anything/knowledge-graph.json` when that directory is present).
    
    ## 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. **Resolve the data directory `$UA_DIR`.** Run `UA_DIR=$([ -d .understand-anything ] && echo .understand-anything || echo .ua)` — this is the legacy `.understand-anything/` when it already exists, otherwise the new `.ua/`. Check that `$UA_DIR/knowledge-graph.json` exists in the current project root. If not, tell the user to run `/understand` first.
    
    2. **Check graph freshness before using graph-derived context**:
       - Read `project.gitCommitHash` from the graph metadata as `GRAPH_COMMIT_RAW`. Resolve it as a commit before using it in any Git diff, then compare it with `git rev-parse HEAD` and inspect project-scoped committed and working-tree changes from the project root:
         ```bash
         GRAPH_COMMIT=$(git rev-parse --verify --end-of-options "${GRAPH_COMMIT_RAW}^{commit}" 2>/dev/null)
         git rev-parse HEAD
         git diff --name-only "$GRAPH_COMMIT" HEAD -- .
         git diff --cached --name-only -- .
         git diff --name-only -- .
         git ls-files --others --exclude-standard -- .
         ```
       - The `-- .` pathspec is required: commits that only touch a sibling monorepo project must not make this graph stale. A hash mismatch alone is not stale when the project diff is empty.
       - Ignore the selected data directory (`.ua/` or legacy `.understand-anything/`) in every command's output because it contains generated graph artifacts, not project source drift.
       - If the committed diff or any working-tree command reports project files, warn before answering that graph-derived context may omit those changes. Suggest: Run `/understand` to refresh the graph.
       - Run the commit diff only when `GRAPH_COMMIT_RAW` resolves successfully. If the graph commit or Git metadata is missing, invalid, or unavailable, give a brief best-effort warning and continue instead of blocking.
    
    3. **Read project metadata only** — use Grep or Read with a line limit to extract just the `"project"` section from the top of the file for context (name, description, languages, frameworks).
    
    4. **Search for relevant nodes** — use Grep to search the knowledge graph file for the user's query keywords: "$ARGUMENTS"
       - Search `"name"` fields: `grep -i "query_keyword"` in the graph file
       - Search `"summary"` fields for semantic matches
       - Search `"tags"` arrays for topic matches
       - Note the `id` values of all matching nodes
    
    5. **Find connected edges** — for each matched node ID, Grep for that ID in the `edges` section to find:
       - What it imports or depends on (downstream)
       - What calls or imports it (upstream)
       - This gives you the 1-hop subgraph around the query
    
    6. **Read layer context** — Grep for `"layers"` to understand which architectural layers the matched nodes belong to.
    
    7. **Answer the query** using only the relevant subgraph:
       - Reference specific files, functions, and relationships from the graph
       - Explain which layer(s) are relevant and why
       - Be concise but thorough — link concepts to actual code locations
       - If the query doesn't match any nodes, say so and suggest related terms from the graph
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/egonex-ai-understand-anything-understand-anything-plugin-skills-understand-chat.md

// REPO STATS

92.4k stars
134 open issues
Last commit: 4d ago