get_blast_radius
Analyze code dependencies to identify what breaks before refactoring, renaming, or deleting functions, files, or modules. Returns risk assessment and all affected callers, endpoints, and operations.
Instructions
Check what breaks BEFORE refactoring, renaming, or deleting a function, file, or module.
CALL THIS WHEN: • You're about to refactor or rename a function — see every caller that needs updating • You want to know if a change is safe — check if anything depends on this code • A PR modifies a shared utility — trace all downstream consumers • You need to assess risk level before a change (LOW/MEDIUM/HIGH)
RETURNS: Risk assessment (LOW/MEDIUM/HIGH), all affected callers grouped by module with file paths, impacted HTTP endpoints, impacted cron jobs, and affected DB operations. Traces up to 5 hops deep through the call graph.
EXAMPLES: • "What breaks if I change the formatMessage function?" • "How many callers does this utility have across the codebase?" • "Is it safe to delete this file or do other modules use it?" • "Which API endpoints are affected if I modify the db module?"
WHY NOT JUST READ FILES: You can grep for direct callers, but you'll miss indirect callers 2-3 hops away, and you won't see affected endpoints or cron jobs. This traces the full transitive dependency chain automatically.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||