This analyzes your git diffs against a pre-built knowledge graph to show you not just what changed, but what else might break. It greps through the graph JSON to find nodes for your changed files, traces their edges to identify upstream callers and downstream dependencies, then gives you a structured breakdown of affected components, architectural layers touched, and a risk assessment based on complexity scores and blast radius. The smart part is it doesn't load the entire graph into context, it searches efficiently. You need to run the understand skill first to generate the graph, then this becomes useful during code review or before merging branches. Outputs a diff overlay JSON that the dashboard can visualize.

skills.sh installs
4K
GitHub stars
91.8K
last updated
Aug 21, 2026

Install

$ npx -y skills add egonex-ai/understand-anything --skill understand-diff --agent claude-code

Installs into .claude/skills of the current project.

Files

/understand-diff

Analyze the current code changes against 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

Sponsors

Details

Repository
github.com/egonex-ai/understand-anything
Category
Git & Pull Requests
First seen
Jun 11, 2026

More from egonex-ai/understand-anything

All 8
1everyinc avatarce-commit-push-preveryinc/compound-engineering-pluginCommit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.3.5Kskills.sh installs
2everyinc avatarce-commiteveryinc/compound-engineering-pluginCreate a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.3.5Kskills.sh installs
3zc277584121 avatargit-get-notificationzc277584121/mygitpluginCheck GitHub notifications and recent Issues/PRs for monitored repos3.4Kskills.sh installs
4everyinc avatarce-resolve-pr-feedbackeveryinc/compound-engineering-pluginResolve PR review feedback. Use when addressing review comments, resolving review threads, or fixing code-review feedback.3.3Kskills.sh installs
5github avatargithub-actions-hardeninggithub/awesome-copilotSecurity hardening reviewer for GitHub Actions workflow files (.github/workflows/*.yml). Reasons about the Actions threat model that pattern matchers and genera2.6Kskills.sh installs
6nvidia avatarmcore-create-issuenvidia/skillsInvestigate a failing GitHub Actions run or job and create a GitHub issue for the failure.1.8Kskills.sh installs