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.Documentation Index
Fetch the complete documentation index at: https://kasava.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
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
- 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
- Create Plan — turn the impact analysis into a structured work plan
- View Code — jump to the relevant files
Example Prompts
| What you ask | What you get |
|---|---|
| ”What’s the blast radius of changing the AuthMiddleware?” | Blast radius card for that symbol |
| ”If I refactor the checkout service, what breaks?” | Codebase impact analysis |
| ”How many files depend on UserRepository?” | Dependency count and list |
| ”Show the impact of removing the legacy payment handler” | Full impact with risk assessment |
| ”What would it take to rename OrderService to PurchaseService?” | Files to update, downstream effects |