lsp-cross-repo

Solid

Cross-repository analysis — find all callers of a library symbol in one or more consumer repos. Use when refactoring a shared library and need to understand how consumers use it.

AI & Automation 56 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
58
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

> Requires the agent-lsp MCP server. # lsp-cross-repo Multi-root cross-repo caller analysis for library + consumer workflows. Finds all usages of a library symbol across one or more consumer codebases in a single call. Read-only — does not modify any files. ## When to use - Before changing a library API: find all callers in every consumer - Before deleting a symbol: verify it has no cross-repo dependents - When a change in repo A might break repo B or C - Auditing how internal packages are used across services Use `/lsp-impact` instead for single-repo blast-radius analysis. ## Workflow ### Step 1 — Initialize the primary workspace Start the language server on the library root if not already running: ``` mcp__lsp__start_lsp({ "root_dir": "/path/to/library" }) ``` ### Step 2 — Locate the library symbol Find the symbol's definition to get `file_path`, `line`, and `column`: ``` mcp__lsp__find_symbol({ "query": "<symbol-name>" }) ``` Pick the result in the library repo (not a test file). ### Step 3 — Find all cross-repo references (primary step) Call `get_cross_repo_references` with the symbol location and all consumer repo roots. This adds each consumer as a workspace folder, waits for indexing, runs `find_references` across all roots, and returns results partitioned by repo: ``` mcp__lsp__get_cross_repo_references({ "symbol_file": "/abs/path/to/library/file.go", "line": <line>, "column": <column>, "consumer_roots": [ "/abs/path/to/consumer-a", "/...

Details

Author
blackwell-systems
Repository
blackwell-systems/agent-lsp
Created
2 months ago
Last Updated
today
Language
Go
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category