lsp-impact

> Requires the agent-lsp MCP server. # lsp-impact Blast-radius analysis for any symbol or file. Discovers all direct references, callers (via call hierarchy), and type relationships before you touch anything. Read-only — does not modify any files. Run this skill **before** lsp-edit-export: impact tells you what exists and how widespread the change is; lsp-edit-export tells you how to execute the change safely. **Invocation:** - **File path** (e.g. `"internal/lsp/client.go"`) → use the File-level entry (Step 0) to surface all exported-symbol impact at once. - **Symbol name** in dot notation (e.g. `"codec.Encode"`, `"Buffer.Reset"`) → skip Step 0; start at Prerequisites, then Step 1. --- ## Step 0 — File-level entry (when user provides a file path) Use this shortcut when the user is changing or auditing an entire file rather than a single symbol. `blast_radius` enumerates all exported symbols in the file, resolves their references, and returns test callers (with enclosing test function names) and non-test callers in a single call. ``` mcp__lsp__blast_radius({ "changed_files": ["/abs/path/to/file.go"], "include_transitive": false // set true to surface second-order callers }) ``` Returns: - `affected_symbols` — each exported symbol with its reference count - `test_callers` — test files + enclosing test function names - `non_test_callers` — production call sites **Decision after Step 0:** | Result | Action | |--------|--------| | 0 non-test callers | Low blast ra...