understand-diff

Analyze git diffs against a knowledge graph to identify affected components.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill understand-diff-cookeyholder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: understand-diff
Source: https://github.com/cookeyholder/django-devcontainer-template/tree/main/.agent/skills/understand-diff
Command: npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill understand-diff-cookeyholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze git diffs or pull requests to understand what changed, which components were affected, and the associated risks.

Core Features & Use Cases

  • Graph-aware diff analysis: map changes to nodes (files, functions, modules) in the knowledge graph.
  • Impact assessment: identify upstream callers, downstream dependencies, and cross-layer effects for risk review.
  • Use Case: When reviewing a PR, quickly see which parts of the system might be impacted and what to test.

Quick Start

Compare the current branch against the base branch and generate a graph-informed impact report.

Frequently Asked Questions about understand-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a git diff for code review and risk assessment?

To analyze a git diff for code review, the Skill parses your pull request changes, locates the affected file nodes in a local knowledge graph, and expands one-hop edges to reveal upstream callers and downstream dependencies for structured risk assessment.

What is graph-aware dependency analysis for pull requests?

Graph-aware dependency analysis maps your pull request changes to nodes in a knowledge graph, then expands one-hop edges to identify upstream callers, downstream dependencies, and cross-layer impacts to guide your risk assessment and testing.

Do I need a knowledge graph file to assess the impact of code changes?

Yes, you need a local knowledge graph located at .understand-anything/knowledge-graph.json. The Skill reads project metadata, nodes, and edges from this file to identify affected components and produce a structured impact report.

How do I identify upstream callers and downstream dependencies when reviewing a PR?

You can identify upstream callers and downstream dependencies by running the Skill against your git diff. It locates changed file nodes within the knowledge graph and expands one-hop edges to reveal cross-layer impacts for your review.

Can I use this for dependency analysis if my project lacks a knowledge graph?

No, dependency analysis requires the knowledge graph at .understand-anything/knowledge-graph.json to function. Without this file containing your project's nodes and edges, the Skill cannot map changes or assess cross-layer impacts.