Agent skill · data analytics · lum1104
understand
Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships
Why this skill is useful
Generates a knowledge graph from a codebase that aids in understanding architecture and relationships, which is not commonly known to AI.
What it needs
Requires understand installed locally. About 10k tokens when loaded. Last updated 2026-07-30. 77,791 stars on the source repository.
What this skill does
/understand Analyze the current codebase and produce a knowledge-graph.json file in the project's data directory (.ua/, or the legacy .understand-anything/ when it already exists). This file powers the interactive dashboard for exploring the project's architecture. Options $ARGUMENTS may contain: --full — Force a full rebuild, ignoring any existing graph --auto-update — Enable automatic graph updates on commit (writes autoUpdate: true to $UADIR/config.json) --no-auto-update — Disable automatic graph updates (writes autoUpdate: false to $UADIR/config.json) --review — Run full LLM graph-reviewer instead of inline deterministic validation --language <lang> — Generate all textual content (summaries, descriptions, tags, titles, languageNotes, languageLesson) in the specified language. Accepts ISO 639-1 codes (zh, ja, ko, en, es, fr, de, etc.) or friendly names (chinese, japanese, korean, english, spanish, etc.). Locale variants supported: zh-TW, zh-HK, etc. Defaults to en (English). Stores preference in $UADIR/config.json for consistency across incremental updates. --exclude <patterns> — Comma-separated glob patterns for additional files/directories to exclude from analysis (e.g., --exclude "tests/,docs/"). These patterns take highest priority over built-in defaults and .understandignore rules. Supports gitignore syntax including ! negation. A directory path (e.g. /path/to/repo or ../other-project) — Analyze the given directory instead of the current working directory --- Progress Reporting Throughout execution, report progress to the user at each phase transition and during batch processing. This keeps users informed on large codebases where analysis can take a long time. Phase transitions: At the start of each phase, print a status line: [Phase N/7] <phase name>... Example: [Phase 2/7] Analyzing files (12 batches)... …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills lum1104/understand