Enumerate exported symbols and cross-check references to identify dead code.
npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-dead-code
Please help me install this Agent Skill. Skill: lsp-dead-code Source: https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-dead-code Command: npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-dead-code
Enumerate exported symbols in a file and surface those with zero references across the workspace, enabling targeted dead-code audits and API cleanup.
Open a target project and run this skill against a file to identify exported symbols with zero references.
High-intent search queries and answers about installing and using this skill.
To find dead code, enumerate exported symbols in a target file and cross-check their references across the workspace to surface zero-reference candidates for cleanup. This process uses LSP to build a structured report identifying unused public interfaces.
The best way to audit APIs before a release is to cross-check exported symbols against workspace references to identify dead code. This generates a zero-reference report with grep-based validation, highlighting unused public interfaces and reducing maintenance surface area.
Yes, dead code analysis applies to multi-language repositories by leveraging the agent-lsp MCP server. It uses get_document_symbols and get_references to audit exported symbols and validate their usage across different languages within the workspace.
Yes, you need the agent-lsp MCP server to detect unused exported symbols. The analysis relies on LSP methods like get_document_symbols and get_references to enumerate exports and cross-check their usage across the workspace.
Static analysis handles dynamic usage patterns by including caveats in the dead code report. While it surfaces zero-reference candidates and test-only references using LSP, it explicitly notes that dynamic usage patterns may not be fully captured by static cross-checking.
Yes, you can identify test-only references during a dead code audit. The analysis produces a structured report that specifically highlights both zero-reference candidates and symbols that are only referenced by tests, ensuring safe refactoring.
open-haxConfigure and register LSP servers for language intelligence in OpenCode.
santosomarIdentify dead code candidates using static analysis and code coverage data.
NeKon69Index LSP commands and reference the plugins.lspconfig module in Neovim.
DayoptDetect and remove unused code, dead imports, and console statements in TypeScript/JavaScript projects.
