lsp-dead-code

Topics in the source

• lsp-dead-code
• When to Use
• What counts as "exported"
• Prerequisites
• Step 0 — Verify indexing is complete (mandatory)
• Step 1 — Open the file and enumerate symbols
• Step 2 — Check references for each exported symbol
• Step 3 — Classify and report

Requires the agent-lsp MCP server. Audit an exported symbol list for zero-reference candidates. Calls listsymbols to enumerate symbols, then checks each exported symbol with findreferences to find callers. Produces a classified report. Use this skill when you want to identify dead code in a file — exported symbols that are defined but never called anywhere in the workspace. Common use cases: Cleaning up APIs before a release Identifying legacy exports that can be safely removed Auditing a package for unused public surface area Important: This skill surfaces candidates. Always review results manually before deleting anything. See the Caveats section below. | 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 LSP is not yet initialized, call mcplspstartlsp with the workspace root first: agent-lsp supports auto-inference f

This is an excerpt. Refer to the complete source and its current requirements.