lsp-cross-repo

Cross-repo caller analysis identifies all call sites of a library symbol across multiple consumer repositories to support refactoring. Initialize and index workspaces across library and consumer repos to gather references efficiently in one pass.

Analyzing the impact of changes across consumer repos requires multi-root cross-repo caller analysis to identify all usages of a library symbol. It provides library_references and consumer_references along with warnings to guide safe changes.

To trace symbol usage across repos, start the LSP server on the library root, locate the symbol, and run the cross-repo reference lookup. You can optionally show call hierarchy and implementations to trace symbol usage across repos.

Yes, cross-repo reference lookup requires an agent-lsp MCP server with cross-repo workspace management and reference lookup capabilities. The LSP server must be started on the library root to initialize and index workspaces across library and consumer repos.

Yes, you can optionally show call hierarchy and implementations to trace symbol usage across repos. This helps enumerate all consumer usages and prevent regressions when analyzing the impact of changes across multiple projects.

Cross-repo reference lookup depends on an agent-lsp MCP server for cross-repo workspace management. It provides library_references, consumer_references, and warnings to guide safe changes, but requires proper workspace initialization and indexing across all consumer repositories to prevent regressions.