lsp-impact

Determine the blast radius of a symbol or file via references, callers, and type relationships.

102|5|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-impact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lsp-impact
Source: https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-impact
Command: npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot.

Core Features & Use Cases

  • Discover all direct references across the workspace for a symbol or file.
  • Surface call hierarchy and type relationships to understand impact before changes.
  • Use case: Assess impact before renaming functions, deleting APIs, or changing signatures.

Quick Start

Provide a file path or symbol name to surface all exported-symbol impact.

Frequently Asked Questions about lsp-impact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find all references and callers before refactoring a function?

Blast-radius analysis determines the full impact of a symbol by surfacing all references, call hierarchy, and type relationships before you refactor. It shows callers and subtypes so you can safely change signatures or delete APIs across the workspace.

What is type hierarchy and call hierarchy impact analysis for code changes?

Impact analysis maps the blast radius of code changes by collecting call hierarchy and type supertypes or subtypes. It reveals every caller and reference count associated with a symbol, ensuring safe refactoring and signature modifications without breaking dependencies.

Can I analyze the blast radius of an entire file to see all exported symbols?

Yes, you can provide a file path to surface all exported-symbol impact in one shot. This analyzes the blast radius for the entire file, showing all references and type relationships for every exported symbol before you make workspace-wide changes.

Do I need an agent-lsp MCP server to run impact analysis?

Yes, impact analysis requires the agent-lsp MCP server to assemble the complete impact surface. It depends on agent-lsp capabilities for references, call hierarchy, and type hierarchy to determine the blast radius safely before refactoring.

What's the best way to ensure safe deletion of APIs across a codebase?

Performing blast-radius analysis is the best way to ensure safe API deletion, as it surfaces all direct references and type relationships. By checking the complete impact surface beforehand, you can verify no callers depend on the deleted method.