lsp-edit-export

> Requires the agent-lsp MCP server. # lsp-edit-export Safe workflow for editing exported symbols. Always discovers all callers before touching any code, then verifies the change is clean. ## When to Use Use this skill whenever you intend to change the signature, name, or behavior of an **exported symbol**: a symbol visible outside its defining package or module. **Language-specific definitions:** | Language | Exported means... | |------------|------------------------------------------------------------------------| | Go | Identifier starts with an uppercase letter (e.g. `MyFunc`, `MyType`) | | TypeScript | Has `export` keyword; or is a public class member (no `private`) | | Python | Not prefixed with `_`; or explicitly listed in `__all__` | | Java/C# | Has `public` or `protected` visibility modifier | | Rust | Has `pub` keyword | If you are unsure whether a symbol is exported, treat it as exported and run this workflow anyway. The cost is a few extra tool calls; the benefit is never breaking a hidden caller. **Do NOT skip this workflow** even when you believe there are zero callers. The confirmation gate in step 3 exists precisely for that case. ## Workflow **If LSP is not yet initialized**, call `mcp__lsp__start_lsp` with the workspace root first. (agent-lsp supports auto-inference from file pa...