Understand Anything

πŸš€ Description

Egonex-AI/Understand-Anything β€” a Claude Code plugin that analyzes a project with a multi-agent pipeline, builds a knowledge graph of every file, function, class, and dependency, then opens an interactive dashboard to explore it visually. MIT. Tagline: β€œgraphs that teach > graphs that impress” β€” the point isn’t to wow you with complexity, it’s to quietly show how the pieces fit.

The framing problem it solves: you join a new team, the codebase is 200k lines, where do you even start? Instead of reading code blind, you get a navigable, searchable, color-coded map.

🧩 Features

  • Structural graph β€” every file/function/class is a clickable node with plain-English summaries, relationships, and guided tours.
  • Domain view β€” maps code to real business processes (domains β†’ flows β†’ steps) as a horizontal graph.
  • /understand-knowledge β€” points at a Karpathy-pattern LLM wiki and builds a force-directed graph with community clustering: parses wikilinks/categories from index.md deterministically, then LLM agents discover implicit relationships and extract entities/claims. (Directly applicable to this vault β†’ Brain.)
  • Guided tours β€” auto-generated walkthroughs ordered by dependency, so you learn in the right order.
  • Fuzzy + semantic search β€” find by name or by meaning (β€œwhich parts handle auth?”).
  • Diff impact analysis (/understand-diff) β€” see which parts your changes touch before you commit.
  • Persona-adaptive UI β€” detail level adjusts for junior dev / PM / power user.
  • Layer visualization β€” auto-grouping by architectural layer (API/Service/Data/UI/Utility).
  • Incremental β€” re-runs only re-analyze changed files; --auto-update patches the graph via a post-commit hook.
  • Localized output β€” --language for en/zh/zh-TW/ja/ko/ru node summaries and dashboard.

πŸ”§ Under the hood

Tree-sitter + LLM hybrid β€” Tree-sitter (deterministic) parses source into a syntax tree and extracts structural facts (imports, exports, defs, call sites, inheritance), pre-resolved into an importMap and used for fingerprint-based change detection. The LLM (semantic) reads that structure plus source to produce summaries, tags, layer assignments, domain mapping, and tours. So the structural side is reproducible while the semantic side captures intent.

Multi-agent pipeline β€” /understand orchestrates 5 agents (project-scanner, file-analyzer, architecture-analyzer, tour-builder, graph-reviewer); /understand-domain adds domain-analyzer; /understand-knowledge adds article-analyzer. File analyzers run up to 5 concurrent, 20–30 files per batch.

The graph is just JSON (.understand-anything/knowledge-graph.json) β€” commit it once and teammates skip the pipeline (track 10 MB+ graphs with git-lfs). Good for onboarding, PR reviews, docs-as-code.

Reasoning for

The natural complement to Graphify β€” both turn code/docs into a queryable knowledge graph, but Understand-Anything leans on a committed-to-repo JSON graph + interactive dashboard for team onboarding rather than token-reduction context. The /understand-knowledge mode is the interesting hook for me: it can ingest a Karpathy-pattern wiki like this very vault (Brain) and surface implicit relationships my index files don’t capture. Worth a pass on Qamera AI / PLSoft codebases for faster onboarding and diff-impact review.

Alternatives considered

  • Graphify β€” code/docs/images β†’ queryable graph with clustering and 71Γ— token reduction (more retrieval/context-engineering oriented).
  • CocoIndex / LightRAG β€” incremental indexing / KG-RAG for agent context, not interactive onboarding dashboards.
  • Google Cloud Knowledge Catalog β€” managed knowledge graph over data, agent-facing via MCP.

Template: tool