What problem does it solve? Reviewing a pull request or branch diff without architectural context makes it hard to judge blast radius, spot cross-layer impacts, and prioritize what to review carefully. ## Core Features & Use Cases - Diff-to-Graph Mapping: Matches changed files from git diff to nodes in the knowledge graph at .understand-anything/knowledge-graph.json. - Impact Analysis: Traces 1-hop import and call edges to find upstream callers and downstream dependencies affected by the change. - Risk Assessment: Reports affected architectural layers, node complexity, and blast radius to guide review focus. - 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 see which layers and components your changes touch and which connected modules might break. ## Quick Start Ask the assistant to analyze the current branch diff against the knowledge graph and summarize the changed components, affected components, and risks.
