What problem does it solve? When modifying unfamiliar code, it is hard to know what will break if you change a function, who already uses a component, or which files are architectural hubs. This Skill builds a local import and call graph of the repository so those questions get concrete answers with file paths and line numbers. ## Core Features & Use Cases - Blast radius analysis: Run graphify affected "useProStatus" to list every file and line impacted by a change to a symbol. - Symbol relationship inspection: Run graphify explain "Btn" to see who calls a symbol and what it calls. - Architecture mapping: Run graphify god-nodes --top 12 to identify the load-bearing nodes of the project. - Use Case: Before creating a new component, check the reuse gate by running affected and explain on existing candidates to see what already exists and who consumes it. ## Quick Start Ask the assistant to build the code graph with graphify and show what would be affected if you modified a specific function or component.