Generate a Code Map with symbol and file analysis via agent-lsp MCP.
npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-understand
Please help me install this Agent Skill. Skill: lsp-understand Source: https://github.com/blackwell-systems/agent-lsp/tree/main/skills/lsp-understand Command: npx skills add https://github.com/blackwell-systems/agent-lsp --skill lsp-understand
Deep-dive exploration of unfamiliar code — given a symbol or file, builds a complete Code Map showing type info, implementations, call hierarchy (2-level depth limit), all references, and source. Broader than lsp-explore: accepts files, synthesizes multi-symbol relationships, and produces a navigable dependency map. Read-only — does not modify any files.
Provide a target file path or symbol path to generate a Code Map for the specified code region.
High-intent search queries and answers about installing and using this skill.
You generate a code map by providing a target file path or symbol path to analyze the code region. The map synthesizes cross-symbol relationships, including internal calls, shared callers, and interface implementations, into a navigable dependency graph.
Call hierarchy analysis maps code dependencies by collecting caller and callee relationships up to a 2-level depth limit. This prevents infinite recursion while revealing how functions interact within the navigable dependency graph.
Yes, an agent-lsp MCP server with a hoverProvider is required to collect type signatures and analyze code references. When available, it also leverages implementationProvider, callHierarchyProvider, and referencesProvider for deeper call graphs and reference collection.
Yes, you can provide a file path using Mode B to build a navigable dependency graph for the entire module. It synthesizes multi-symbol relationships across the file, including internal calls, shared callers, and interface implementations.
No, generating a code map is a read-only process that does not modify any files. It only collects type information, implementations, call hierarchy, and all references to produce a structured map and a navigable dependency graph.
Unlike lsp-explore, this approach accepts file paths and synthesizes multi-symbol relationships to produce a broader navigable dependency map. It reveals internal calls, shared callers, and interface implementations across the entire module or project.
blackwell-systemsDetermine the blast radius of a symbol or file via references, callers, and type relationships.
wangke19Map codebases from architecture to implementation with call graphs.
chriskrychoPerform semantic search and relationship mapping across codebases.
StrategicMilkMap codebases via LSP symbol navigation and return structured JSON reports.
