skills.rest
blackwell-systems
blackwell-systemsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

lsp-edit-export

Locate all call sites before editing exported symbols with impact confirmation.

102|5|Updated Apr 6, 2026
Search Tags:#lsp#code-change#symbol-edit#reference-search#safety-guard#exported-symbols#caller-analysis
One-click install
npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-edit-export
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lsp-edit-export
Source: https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-edit-export
Command: npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-edit-export

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Editing exported symbols like function signatures or public types can cause breakages for external callers if changes are made without understanding all dependencies. This Skill provides a safe, multi-step workflow that discovers all callers, gates changes with an explicit impact check, and validates that the change doesn't introduce regressions.

Core Features & Use Cases

  • Caller discovery: automatically locate all call sites before applying any edits to an exported symbol.
  • Impact gating: present an explicit confirmation gate showing where and how many call sites exist before proceeding.
  • End-to-end safety checks: apply the edit, collect diagnostics, and perform a rebuild to ensure no new errors are introduced.
  • Use case: when renaming or changing a public API in a library, ensuring downstream callers are updated safely.

Quick Start

Initiate the workflow to locate the symbol, review all callers, confirm impact, apply the safe edit, then validate with diagnostics and a rebuild.

Frequently Asked Questions about lsp-edit-export

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

FAQPage Schema
How do I safely rename an exported function without breaking callers?▼

Editing exported symbols like public APIs can break external callers if changes are made without understanding all dependencies. You need caller discovery and impact gating to safely apply edits and validate that no new errors are introduced.

How do I find all call sites before changing a public API in TypeScript or Go?▼

Caller discovery is the process of automatically locating all call sites before applying any edits to an exported symbol. It uses an agent-lsp MCP server with the referencesProvider capability to surface caller data for impact gating.

Do I need an agent-lsp MCP server to gate edits to exported symbols?▼

Yes, an agent-lsp MCP server is required. It must support the referencesProvider capability to surface caller data, locate symbols, discover callers, and perform build validation for languages with exported APIs like Go, TypeScript, Python, Java/C#, and Rust.

What is the best way to change a public type signature in a library?▼

The best approach is a multi-step workflow: locate the symbol, review all callers, confirm impact, apply the safe edit, then validate with diagnostics and a rebuild. This end-to-end safety check ensures no new errors are introduced when changing public APIs.

How do I validate that an exported symbol edit doesn't introduce regressions?▼

You validate edits by applying the change, collecting diagnostics, and performing a rebuild. This end-to-end safety check ensures that editing exported symbols does not introduce new errors or regressions for downstream callers.

When should I not use an automated reference search for API changes?▼

You should not use this workflow when your language server lacks the referencesProvider capability. Without an agent-lsp MCP server to surface caller data, this workflow cannot discover all call sites or gate edits with an explicit impact check.

Related Skills

Explore More Software Engineering Skills→
zlzforeverzlzforever
1

add-serena

Integrate Serena MCP into projects for LSP-based code understanding and symbol navigation.

Community
Intermediate
blackwell-systemsblackwell-systems
102

lsp-verify

Verify LSP diagnostics, build, and tests after code edits.

Community
Advanced
TitusLee2000TitusLee2000

remotecamera-orchestrator

Orchestrate RemoteCamera stack builds with server, client, dashboard, and tests.

Community
Advanced
ElliotJLTElliotJLT
60

trace-it

Traces callers and dependents before editing shared code to map impact.

Community
Basic