claudegoodies
Skill

understand

From Egonex-AI

Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships

Scans a codebase to build a knowledge-graph.json powering an interactive architecture dashboard.

Use it when

  • Onboarding to an unfamiliar repo and need an architecture overview
  • Want auto-updating dependency/component graph on each commit
  • Need docs generated in a specific language (zh, ja, ko, es, etc.)
  • Analyzing a repo outside the current working directory

Skip it if

  • Requires building @understand-anything/core via Node on first run
  • Depends on git worktree/repo detection logic that may misresolve paths
  • Tied to its own plugin install layout across Claude, Copilot, Codex environments

Facts

Status
Actively maintained
Last commit

Source preview

The instructions Claude Code reads when this skill runs.

# /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 `$UA_DIR/config.json`)
  - `--no-auto-update` — Disable automatic graph updates (writes `autoUpdate: false` to `$UA_DIR/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 `$UA_DIR/config.json` for consistency across incremental updates.
  - 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 tr
View full source on GitHub →

Other skills