What problem does it solve? When reviewing code changes or pull requests, it is hard to know which components, layers, and downstream dependencies a diff actually touches. This Skill maps changed files onto the project's knowledge graph so you can see the blast radius of a change before merging. ## Core Features & Use Cases - Changed Component Mapping: Matches files from git diff to nodes in the knowledge graph (knowledge-graph.json) to identify exactly what was modified. - Impact Analysis: Follows 1-hop edges (imports, calls, depends_on) to surface upstream callers and downstream dependencies that might break. - Risk Assessment: Uses node complexity, cross-layer edges, and blast radius to highlight what needs careful review. - Dashboard Overlay: Writes a diff-overlay.json file so the understand dashboard can visualize changed and affected components. - Use Case: Before merging a feature branch, run the analysis to discover that a small utility change also affects three services in another architectural layer. ## Quick Start Ask the assistant to analyze the current branch's changes against the knowledge graph and show which components and layers are affected.
