hulde-diff

/hulde-diff

Analyze the current code changes against the knowledge graph at .hulde-review/knowledge-graph.json.

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?}
  • Node types: file, function, class, module, concept
  • IDs: file:path, func:path:name, class:path:name
• edges[] — each has {source, target, type, direction, weight}
  • Key types: imports, contains, calls, depends_on
• layers[] — each has {id, name, description, nodeIds[]}
• tour[] — each has {order, title, description, nodeIds[]}

How to Read Efficiently

1. Use Grep to search within the JSON for relevant entries BEFORE reading the full file
2. Only read sections you need — don't dump the entire graph into context
3. Node names and summaries are the most useful fields for understanding
4. Edges tell you how components connect — follow imports and calls for dependency chains

Instructions

1. Check that .hulde-review/knowledge-graph.json exists. If not, tell the user to run /hulde-review first.

2. Get the changed files list (do NOT read the graph yet):

   • If on a branch with uncommitted changes: git diff --name-only
   • If on a feature branch: git diff main...HEAD --name-only (or the base branch)
   • If the user specifies a PR number: get the diff from that PR

3. Read project metadata only — use Grep or Read with a line limit to extract just the "project" section for context.

4. Find nodes for changed files — for each changed file path, use Grep to search the knowledge graph for:

   • Nodes with matching "filePath" values (e.g., grep "changed/file/path")
   • This finds file nodes AND function/class nodes defined in those files
   • Note the id values of all matched nodes

5. Find connected edges (1-hop) — for each matched node ID, Grep for that ID in the edges to find:

   • What imports or depends on the changed nodes (upstream callers)
   • What the changed nodes import or call (downstream dependencies)
   • These are the "affected components" — things that might break or need updating