Skip to main content
Before you refactor a function, rename a service, or swap a dependency, ask the Agent what will break. It traces your symbol graph to show every file, component, and downstream consumer affected by a change.

​
What You Get

​
Blast Radius

An impact card showing exactly what a change to a specific symbol affects:
  • Direct dependents — files that directly import or call the symbol
  • Transitive dependents — the ripple effect through the dependency chain
  • Affected files — full list with file paths
  • Risk level — low, medium, or high based on the scope of impact
Action buttons let you:
  • Find All Usages — see every reference
  • Show Call Graph — visualize the dependency chain
  • Create Tracking Issue — turn the analysis into a tracked work item

​
Codebase Impact

A broader analysis when your change spans multiple areas:
  • Affected layers — which architectural layers are touched (API, service, data, UI)
  • Reusable components — shared components that need updating
  • Reference patterns — how the symbol is typically used
  • Blast radius summary — aggregate risk assessment
Action buttons:
  • Create Plan — turn the impact analysis into a structured work plan
  • View Code — jump to the relevant files

​
Example Prompts

​
Why It Matters

Stop breaking things you didn’t know existed. Most refactors fail not because the change is wrong, but because the developer didn’t know about a consumer three layers deep. The Agent traces your actual symbol graph — not guesses — to show real dependencies.
This works best after your repository is indexed. The Agent uses tree-sitter parsing, symbol graphs, and call chains — not just text search.