UN

understand-anything-knowledge-graph

Transforms any project into an interactive knowledge graph and React dashboard for visual navigation.

Install

mkdir -p .claude/skills/understand-anything-knowledge-graph && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11264" && unzip -o skill.zip -d .claude/skills/understand-anything-knowledge-graph && rm skill.zip

Installs to .claude/skills/understand-anything-knowledge-graph

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Turn any codebase into an interactive knowledge graph using Claude Code skills — explore, search, and ask questions about any project visually.
143 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Maps codebase structure
  • Generates interactive knowledge graph
  • Provides plain-English summaries
  • Supports semantic search
  • Generates onboarding tours

How it works

The tool runs a multi-agent pipeline to analyze files, functions, and dependencies, building a graph that is visualized in a React dashboard.

Inputs & outputs

You give it
Codebase directory
You get back
Interactive knowledge graph dashboard

When to use understand-anything-knowledge-graph

  • Explore complex codebase structure
  • Generate onboarding guide for new projects
  • Visualize dependency chains
  • Ask questions about project architecture

About this skill

Understand Anything — Codebase Knowledge Graph

Skill by ara.so — Daily 2026 Skills collection.

Understand Anything is a Claude Code plugin that runs a multi-agent pipeline over your project, builds a knowledge graph of every file, function, class, and dependency, and opens an interactive React dashboard for visual exploration. It produces plain-English summaries of every node so anyone — developer, PM, or designer — can understand the codebase.


Installation

Via Claude Code plugin marketplace

/plugin marketplace add Lum1104/Understand-Anything
/plugin install understand-anything

From source (development)

git clone https://github.com/Lum1104/Understand-Anything
cd Understand-Anything
pnpm install
pnpm --filter @understand-anything/core build
pnpm --filter @understand-anything/skill build
pnpm --filter @understand-anything/dashboard build

Core Skills / Commands

CommandWhat it does
/understandRun the full multi-agent analysis pipeline on the current project
/understand-dashboardOpen the interactive knowledge graph dashboard
/understand-chat <question>Ask anything about the codebase in natural language
/understand-diffAnalyze impact of current uncommitted changes
/understand-explain <path>Deep-dive explanation of a specific file or function
/understand-onboardGenerate an onboarding guide for new team members

Typical Workflow

1. Analyze a project

# Inside any project directory, in Claude Code:
/understand

This orchestrates 5 agents in sequence (with file-analyzers running up to 3 concurrent):

  1. project-scanner — discovers files, detects languages/frameworks
  2. file-analyzer — extracts functions, classes, imports; builds graph nodes and edges
  3. architecture-analyzer — groups nodes into architectural layers (API, Service, Data, UI, Utility)
  4. tour-builder — generates ordered learning tours
  5. graph-reviewer — validates referential integrity

Output is saved to .understand-anything/knowledge-graph.json in your project root.

2. Open the dashboard

/understand-dashboard

The React + Vite dashboard opens in your browser. Features:

  • Graph view — React Flow canvas, color-coded by layer, zoom/pan
  • Node inspector — click any node for code, relationships, LLM summary
  • Search — fuzzy + semantic search across all nodes
  • Tours — guided walkthroughs ordered by dependency
  • Persona mode — toggle detail level (Junior Dev / PM / Power User)

3. Ask questions

/understand-chat How does authentication work in this project?
/understand-chat What calls the payment service?
/understand-chat Which files are most depended on?

4. Review diff impact before committing

# After making changes:
/understand-diff

Returns a list of affected nodes in the knowledge graph — shows ripple effects before you push.

5. Explain a specific file

/understand-explain src/auth/login.ts
/understand-explain src/services/PaymentService.ts

Knowledge Graph Schema

The graph is stored at .understand-anything/knowledge-graph.json. Key types (from packages/core):

// packages/core/src/types.ts

interface GraphNode {
  id: string;                    // unique: "file:src/auth/login.ts"
  type: "file" | "function" | "class" | "module";
  name: string;
  filePath: string;
  layer: ArchitectureLayer;      // "api" | "service" | "data" | "ui" | "utility"
  summary: string;               // LLM-generated plain-English description
  code?: string;                 // raw source snippet
  language?: string;
  concepts?: LanguageConcept[];  // e.g. "generics", "closures", "decorators"
  metadata?: Record<string, unknown>;
}

interface GraphEdge {
  id: string;
  source: string;                // node id
  target: string;                // node id
  type: "imports" | "calls" | "extends" | "implements" | "uses";
  label?: string;
}

interface KnowledgeGraph {
  version: string;
  generatedAt: string;
  projectRoot: string;
  nodes: GraphNode[];
  edges: GraphEdge[];
  tours: GuidedTour[];
}

type ArchitectureLayer = "api" | "service" | "data" | "ui" | "utility" | "unknown";

type LanguageConcept =
  | "generics"
  | "closures"
  | "decorators"
  | "async-await"
  | "interfaces"
  | "higher-order-functions"
  | "dependency-injection"
  | "observers"
  | "iterators"
  | "pattern-matching"
  | "monads"
  | "currying";

Working with the Core Package Programmatically

import { loadKnowledgeGraph, searchGraph, buildTour } from "@understand-anything/core";

// Load the persisted graph
const graph = await loadKnowledgeGraph(".understand-anything/knowledge-graph.json");

// Fuzzy search across all nodes
const results = searchGraph(graph, "payment processing");
console.log(results.map(r => `${r.type}:${r.name} (${r.filePath})`));

// Find all callers of a function
const paymentNode = graph.nodes.find(n => n.name === "processPayment");
const callers = graph.edges
  .filter(e => e.target === paymentNode?.id && e.type === "calls")
  .map(e => graph.nodes.find(n => n.id === e.source));

// Get all nodes in the service layer
const serviceNodes = graph.nodes.filter(n => n.layer === "service");

// Build a guided tour starting from a specific node
const tour = buildTour(graph, { startNodeId: "file:src/index.ts" });
tour.steps.forEach((step, i) => {
  console.log(`Step ${i + 1}: ${step.node.name} — ${step.node.summary}`);
});

Dashboard Development

# Start the dashboard dev server (hot reload)
pnpm dev:dashboard

# Build for production
pnpm --filter @understand-anything/dashboard build

The dashboard is a Vite + React 18 app using:

  • React Flow — graph canvas rendering
  • Zustand — graph state management
  • TailwindCSS v4 — styling
  • Fuse.js — fuzzy search
  • web-tree-sitter — in-browser AST parsing
  • Dagre — automatic graph layout

Project Structure

understand-anything-plugin/
├── .claude-plugin/          # Plugin manifest (read by Claude Code)
├── agents/                  # Agent definitions (project-scanner, file-analyzer, etc.)
├── skills/                  # Skill definitions (/understand, /understand-chat, etc.)
├── src/                     # Plugin TypeScript source
│   ├── context-builder.ts   # Builds LLM context from the graph
│   └── diff-analyzer.ts     # Git diff → affected nodes
├── packages/
│   ├── core/                # Analysis engine
│   │   ├── src/
│   │   │   ├── types.ts     # GraphNode, GraphEdge, KnowledgeGraph
│   │   │   ├── persistence.ts
│   │   │   ├── search.ts    # Fuzzy + semantic search
│   │   │   ├── tours.ts     # Tour generation
│   │   │   ├── schema.ts    # Zod validation schemas
│   │   │   └── tree-sitter.ts
│   │   └── tests/
│   └── dashboard/           # React dashboard app
│       └── src/

Incremental Updates

Re-running /understand only re-analyzes files that changed since the last run (based on mtime and content hash stored in the graph metadata). For large monorepos this makes subsequent runs fast.

To force a full re-analysis:

rm -rf .understand-anything/
/understand

Development Commands

pnpm install                                        # Install all dependencies
pnpm --filter @understand-anything/core build       # Build core package
pnpm --filter @understand-anything/core test        # Run core tests
pnpm --filter @understand-anything/skill build      # Build plugin package
pnpm --filter @understand-anything/skill test       # Run plugin tests
pnpm --filter @understand-anything/dashboard build  # Build dashboard
pnpm dev:dashboard                                  # Dashboard dev server with HMR

Common Patterns

Before a code review

# See what your diff actually touches in the architecture
/understand-diff

Onboarding a new engineer

# Generate a structured onboarding doc grounded in the real code
/understand-onboard

Researching a feature area

/understand-chat What are all the entry points for the GraphQL API?
/understand-explain src/graphql/resolvers/

Understanding an unfamiliar module

/understand-explain src/workers/queue-processor.ts
# Returns: summary, key functions, what calls it, what it calls, concepts used

Troubleshooting

/understand times out on large repos

  • The file-analyzer runs up to 3 workers concurrently. Very large repos (>50k files) may need patience. Delete .understand-anything/ and re-run if a previous run was interrupted.

Dashboard doesn't open

  • Run pnpm --filter @understand-anything/dashboard build first if working from source, then retry /understand-dashboard.

Stale graph after major refactor

  • Delete .understand-anything/knowledge-graph.json to force full re-analysis: rm .understand-anything/knowledge-graph.json && /understand

pnpm install fails with workspace errors

  • Ensure you are using pnpm v8+: pnpm --version. The project uses pnpm workspaces defined in pnpm-workspace.yaml.

Search returns no results

  • Confirm the graph was generated: cat .understand-anything/knowledge-graph.json | head -5. If empty or missing, run /understand first.

Contributing

# Fork, then:
git checkout -b feature/my-feature
pnpm --filter @understand-anything/core test   # must pass
# open a PR — file an issue first for major changes

License: MIT © Lum1104

When not to use it

  • Very large repositories (>50k files) without patience
  • Non-codebase projects

Prerequisites

pnpm

Limitations

  • Large repositories may time out
  • Requires graph generation before search

How it compares

It provides a visual, navigable knowledge graph of the codebase, rather than just text-based documentation.

Compared to similar skills

understand-anything-knowledge-graph side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
understand-anything-knowledge-graph (this skill)04moReviewIntermediate
software-architecture3336moNo flagsIntermediate
codex322moReviewAdvanced
game-development706moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

software-architecture

davila7

Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.

333868

codex

Lucklyric

Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.

32238

game-development

davila7

Game development orchestrator. Routes to platform-specific skills based on project needs.

70195

senior-fullstack

davila7

Comprehensive fullstack development skill for building complete web applications with React, Next.js, Node.js, GraphQL, and PostgreSQL. Includes project scaffolding, code quality analysis, architecture patterns, and complete tech stack guidance. Use when building new projects, analyzing code quality, implementing design patterns, or setting up development workflows.

35110

command-name

anthropics

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

697

python-project-structure

wshobson

Python project organization, module architecture, and public API design. Use when setting up new projects, organizing modules, defining public interfaces with __all__, or planning directory layouts.

860

Search skills

Search the agent skills registry