impact_analysis
Analyze the blast radius of code changes by identifying callers, callees, and risk before modifying or renaming symbols or files.
Instructions
BEFORE modifying/renaming: callers (blast radius), callees, risk (caller-count blast). Line-level? call_chain. Simple edit? read_symbol+write_symbol. AUTO-FRESH: files modified after last index are re-indexed automatically on read — explicit reindex only needed for brand-new workspaces/files.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | Path rel to root (not absolute, not a dir) | |
| depth | No | Indirect caller BFS depth (default: 2, max: 10). Only used when symbol is provided. | |
| symbol | No | Symbol to analyze (fn/class/method/var). Omit → file-level. Use symbols[] for batch. | |
| symbols | No | Multiple symbol names to analyze in one call. Returns array of results. Mutually exclusive with symbol. | |
| change_type | No | Change type. Affects risk threshold (default: modify) | |
| max_callers | No | Max callers to return (default: 20). caller_count always includes full counts. Backward-compat alias for max_results. | |
| max_results | No | Y002-S4 output budget: max results to return (default 20, 0=unlimited). max_callers is a backward-compat alias. | |
| context_mode | No | Y002-S4 output budget: caller context granularity. none=no context (cheapest), snippet, full (default). | |
| workspace_dir | Yes | REQUIRED: project root (abs). reindex first if new. |