Agent skill

Lsp Cross Repo

by blackwell-systems in blackwell-systems/agent-lsp

Cross-repository analysis — find all callers of a library symbol in one or more consumer repos.

MITAuto-check passedDevelopment

Install Lsp Cross Repo

skills CLI
$ npx skills add blackwell-systems/agent-lsp --skill lsp-cross-repo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install blackwell-systems/agent-lsp lsp-cross-repo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/blackwell-systems/agent-lsp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lsp-cross-repo .claude/skills/lsp-cross-repo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lsp-cross-repo
GitHub stars
160
Token cost
~1.1k tokens
SKILL.md length
308 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Cross-repository analysis — find all callers of a library symbol in one or more consumer repos.

  • Works in 4 steps: Initialize the primary workspace → Locate the library symbol → Find all cross-repo references (primary… → …
  • Refactoring a shared library and need to understand how consumers use it
  • SKILL.md covers When to use, Workflow, Output format and Decision guide, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lsp Cross Repo is an agent skill from blackwell-systems/agent-lsp. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)

It sits in Development, covering Refactoring. The repository describes itself as: MCP server that orchestrates language servers into agent-native workflows. 65 tools, 30 CI-verified languages. The licence is MIT.

When your agent uses it

  • Refactoring a shared library and need to understand how consumers use it
  • Tasks that involve Refactoring

Example prompts

  • “/lsp-cross-repo”

Requirements

  • Compatibility (from SKILL.md): Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
  • Pre-approved tools (allowed-tools): mcp__lsp__start_lsp, mcp__lsp__find_symbol, mcp__lsp__get_cross_repo_references, mcp__lsp__add_workspace_folder, mcp__lsp__list_workspace_folders, mcp__lsp__go_to_implementation, mcp__lsp__find_callers, mcp__lsp__inspect_symbol

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Initialize the primary workspace
  2. Locate the library symbol
  3. Find all cross-repo references (primary step)
  4. Callers and implementations (optional)

What it can do on your machine

Read from SKILL.md and the folder at commit 38ca488. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • mcp__lsp__start_lsp
    • mcp__lsp__find_symbol
    • mcp__lsp__get_cross_repo_references
    • mcp__lsp__add_workspace_folder
    • mcp__lsp__list_workspace_folders
    • mcp__lsp__go_to_implementation
    • mcp__lsp__find_callers
    • mcp__lsp__inspect_symbol

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)

    From compatibility in the SKILL.md frontmatter.

Context cost

Lsp Cross Repo loads about 1.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 308 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from blackwell-systems/agent-lsp at commit 38ca488, republished under its MIT licence (© blackwell-systems). 308 words, ~1,098 tokens.

Download SKILL.mdSave it as .claude/skills/lsp-cross-repo/SKILL.md (or your agent's skills folder).
name
lsp-cross-repo
description
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.
allowed-tools
mcp__lsp__start_lsp, mcp__lsp__find_symbol, mcp__lsp__get_cross_repo_references, mcp__lsp__add_workspace_folder, mcp__lsp__list_workspace_folders, mcp__lsp__go_to_implementation, mcp__lsp__find_callers, mcp__lsp__inspect_symbol
compatibility
Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp)
argument-hint
[symbol-name] in [library-file:line:col] used by [consumer-root ...]
user-invocable
true
license
MIT
metadata.required-capabilities
referencesProvider
metadata.optional-capabilities
implementationProvider callHierarchyProvider workspaceSymbolProvider

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",
    "/abs/path/to/consumer-b"
  ]
})

Returns:

  • library_references — usages within the library itself
  • consumer_references — a map of consumer-root → [file:line ...]
  • warnings — any roots that could not be indexed (check these manually)

Decision after Step 3:

ResultAction
No consumer refsSafe to change — verify warnings is empty first
Consumer refs foundRun /lsp-impact on each call site before editing
warnings non-emptyRe-add that root manually and retry Step 3
Step 4 — Callers and implementations (optional)

For a deeper look at how consumers call the symbol:

mcp__lsp__find_callers({
  "file_path": "<library-file>",
  "line": <line>,
  "column": <column>,
  "direction": "incoming"
})

For interfaces — all consumer-side implementations:

mcp__lsp__go_to_implementation({
  "file_path": "<library-file>",
  "line": <line>,
  "column": <column>
})

Output format

## Library-internal references
- file:line — brief context

## Consumer references

### /path/to/consumer-a
- file:line — brief context

### /path/to/consumer-b
- file:line — brief context

Decision guide

SituationAction
No consumer refs, warnings emptySafe to change
Consumer refs foundRun /lsp-impact on each call site before editing
warnings lists a consumer rootThat root failed indexing — check LSP logs
Consumer uses interface, not concrete typeUse go_to_implementation to find all implementors

Example

# Refactoring ParseConfig in a shared config library used by 3 services

start_lsp(root_dir="/repos/config-lib")
find_symbol(query="ParseConfig")        # find definition → file:42:6
get_cross_repo_references(
  symbol_file="/repos/config-lib/pkg/config/parser.go",
  line=42, column=6,
  consumer_roots=["/repos/api-service", "/repos/worker-service", "/repos/batch-job"]
)
# → library_references: 2
# → consumer_references: {api-service: [main.go:14, app.go:31], worker-service: [runner.go:8]}
# → warnings: []

© blackwell-systems, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/lsp-cross-repo of blackwell-systems/agent-lsp.

Open the folder on GitHubat commit 38ca488

Compare with similar skills

Lsp Cross Repo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lsp Cross Repo compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lsp Cross Repo this skillblackwell-systems/agent-lsp160—~1.1kAutomated safety check: PassMIT
Guidelinesakash-network/node1.1k20 repos~577Automated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Component Refactoringlangflow-ai/langflow155k—~3.5kAutomated safety check: PassMIT
Ponytail Lazy Developer ModeDietrichGebert/ponytail160k1 repos~873Automated safety check: PassMIT
ast-grep Structural Searchcode-yeongyu/oh-my-openagent70k—~3.3kAutomated safety check: PassMIT

Similar skills

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 20 repos~577 tokens
    DevelopmentAuto-check passed
  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Component Refactoring

    langflow-ai/langflow

    Refactor high-complexity React components in Langflow frontend.

    155k GitHub stars~3.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Ponytail Lazy Developer Mode

    DietrichGebert/ponytail

    Makes the agent pick the laziest solution that works: skip unneeded work, reuse what exists, prefer the standard library and platform features, and keep diffs small.

    160k GitHub starsUsed in 1 repo~873 tokens
    DevelopmentAuto-check passed
  • ast-grep Structural Search

    code-yeongyu/oh-my-openagent

    Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.

    70k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed

More from blackwell-systems/agent-lsp

All 24 skills in this repo
  • Lsp Dead Code

    blackwell-systems/agent-lsp

    Enumerate exported symbols in a file and surface those with zero references across the workspace.

    160 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Lsp Edit Export

    blackwell-systems/agent-lsp

    Safe workflow for editing exported symbols or public APIs. An agent skill from blackwell-systems/agent-lsp.

    160 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Lsp Fix All

    blackwell-systems/agent-lsp

    Apply available quick-fix code actions for all current diagnostics in a file, one at a time with re-collection between each fix.

    160 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Lsp Generate

    blackwell-systems/agent-lsp

    Trigger language server code generation — implement interface stubs, generate test skeletons, add missing methods, generate mock types.

    160 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Lsp Impact

    blackwell-systems/agent-lsp

    Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it.

    160 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Lsp Rename

    blackwell-systems/agent-lsp

    Two-phase safe rename across the entire workspace. An agent skill from blackwell-systems/agent-lsp.

    160 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Lsp Cross Repo

What does Lsp Cross Repo do?

Cross-repository analysis — find all callers of a library symbol in one or more consumer repos. Lsp Cross Repo is an agent skill from blackwell-systems/agent-lsp. Cross-repository analysis — find all callers of a library symbol in one or more consumer repos.

When should I use Lsp Cross Repo?

Lsp Cross Repo fits situations like: refactoring a shared library and need to understand how consumers use it; tasks that involve Refactoring.

How do I install Lsp Cross Repo in Claude Code?

Run `npx skills add blackwell-systems/agent-lsp --skill lsp-cross-repo -a claude-code`. Or copy the skill folder (skills/lsp-cross-repo in blackwell-systems/agent-lsp) into .claude/skills/lsp-cross-repo in your project. Claude Code loads it when a task matches its description.

How do I install Lsp Cross Repo in Codex?

Run `npx skills add blackwell-systems/agent-lsp --skill lsp-cross-repo -a codex`. Or copy the skill folder (skills/lsp-cross-repo in blackwell-systems/agent-lsp) into .agents/skills/lsp-cross-repo in your project. Codex loads it when a task matches its description.

Can I use Lsp Cross Repo in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blackwell-systems/agent-lsp --skill lsp-cross-repo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lsp-cross-repo, .gemini/skills/lsp-cross-repo, .github/skills/lsp-cross-repo and .opencode/skills/lsp-cross-repo in your project.

What does Lsp Cross Repo need to run?

SKILL.md names no scripts, command-line tools or credentials: Lsp Cross Repo is instructions for the agent only. Its frontmatter pre-approves these tools: mcp__lsp__start_lsp, mcp__lsp__find_symbol, mcp__lsp__get_cross_repo_references, mcp__lsp__add_workspace_folder, mcp__lsp__list_workspace_folders, mcp__lsp__go_to_implementation, mcp__lsp__find_callers, mcp__lsp__inspect_symbol. Compatibility (from SKILL.md): Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp).

Does Lsp Cross Repo access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lsp Cross Repo safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lsp Cross Repo use?

Lsp Cross Repo is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lsp Cross Repo use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lsp Cross Repo?

Skills that share tags, products or a category with Lsp Cross Repo: Guidelines (akash-network/node, 1.1k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Component Refactoring (langflow-ai/langflow, 155k stars) and Ponytail Lazy Developer Mode (DietrichGebert/ponytail, 160k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lsp Cross Repo?

blackwell-systems (a GitHub user) maintains it in blackwell-systems/agent-lsp, which has 160 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 10, 2026.

Source: blackwell-systems/agent-lsp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.