Index of every page on this site: llms.txt
All skills
github avatar

/lsp-setup

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Enable code intelligence (go-to-definition, find-references, hover, type info) for any programming language by installing and configuring an LSP server for Copilot CLI. Detects the OS, installs the right server, and generates the JSON configuration (user-level or repo-level). Use when you need deeper code understanding and no LSP server is configured, or when the user asks to set up, install, or configure an LSP server.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/lsp-setup

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈109 tokens for metadata: the name and description. ≈970 when used: this file. ≈3.6k more on demand in 2 files.

Description uses 5.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈435 characters, or 5.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

LSP Setup for GitHub Copilot CLI

UTILITY SKILL — installs and configures Language Server Protocol servers for Copilot CLI. USE FOR: "setup LSP", "install language server", "configure LSP for Java", "add TypeScript LSP", "enable code intelligence", "I need go-to-definition", "find references not working", "need better code understanding" DO NOT USE FOR: general coding tasks, IDE/editor LSP configuration, non-Copilot-CLI setups

Workflow

  1. Ask the language — use ask_user to ask which programming language(s) the user wants LSP support for
  2. Detect the OS — run uname -s (or check for Windows via $env:OS / %OS%) to determine macOS, Linux, or Windows
  3. Look up the LSP server — read references/lsp-servers.md for known servers, install commands, and config snippets (for Java, also read references/java-jdtls.md)
  4. Ask scope — use ask_user to ask whether the config should be user-level (~/.copilot/lsp-config.json) or repo-level (.github/lsp.json)
  5. Install the server — run the appropriate install command for the detected OS
  6. Write the config — merge the new server entry into the chosen config file (~/.copilot/lsp-config.json for user-level; .github/lsp.json for repo-level). Create the file if missing and preserve existing entries.
  7. Verify — confirm the LSP binary is on $PATH and the config file is valid JSON

Configuration Format

Copilot CLI reads LSP configuration from user-level or repo-level locations, and repo-level config takes precedence over user-level config:

  • User-level: ~/.copilot/lsp-config.json
  • Repo-level: .github/lsp.json (a bare lsp.json at the repo root is not read: with Copilot CLI 1.0.95, copilot lsp list listed servers from .github/lsp.json but not from a root lsp.json)

The JSON structure:

{
  "lspServers": {
    "<server-key>": {
      "command": "<binary>",
      "args": ["--stdio"],
      "fileExtensions": {
        ".<ext>": "<languageId>",
        ".<ext2>": "<languageId>"
      }
    }
  }
}

Key rules

  • command is the binary name (must be on $PATH) or an absolute path.
  • args almost always includes "--stdio" to use standard I/O transport.
  • fileExtensions maps each file extension (with leading dot) to a Language ID.
  • Multiple servers can coexist in lspServers.
  • When merging into an existing file, never overwrite other server entries — only add or update the target language key.

Behavior

  • Always use ask_user with choices when asking the user to pick a language or scope.
  • If the language is not listed in references/lsp-servers.md, search the web for "<language> LSP server" and guide the user through manual configuration.
  • If a package manager is not available (e.g. no Homebrew on macOS), suggest alternative install methods from the reference file.
  • After installation, run which <binary> (or where.exe on Windows) to confirm the binary is accessible.
  • Show the user the final config JSON before writing it.
  • If the config file already exists, read it first and merge — do not clobber.

Verification

After setup, tell the user:

  1. Type /exit to quit Copilot CLI — this is required so the new LSP configuration is loaded on next launch
  2. Re-launch copilot in a project with files of the configured language
  3. Run /lsp to check the server status
  4. Try code intelligence features like go-to-definition or hover

Java

For Java semantic navigation, prefer the lsp tool (goToDefinition, findReferences, hover, incomingCalls) over grep/view once a server is configured. LSP is optional for Java and is not a prerequisite for build or runtime diagnostics. See references/java-jdtls.md for setup details and troubleshooting.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning27d4 checks · Risk SAFE
  • Gen Agent Trust Hub27d

    This skill automates the installation and configuration of Language Server Protocol (LSP) servers to provide advanced code intelligence features. It uses standard package managers and official download sites to fetch well-known development tools from reputable sources.

  • Socket27d

    No alerts

  • Snyk27d

    Risk: MEDIUM · 1 issue

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
  • TypeScript
  • Python
  • lsp
  • language-server
  • copilot-cli
  • code-intelligence
  • setup
  • configuration
  • go-to-definition
  • java

README badge

README badge for github/awesome-copilot/lsp-setup

Installs and configures Language Server Protocol servers for Copilot CLI, enabling go-to-definition, find-references, and hover information. Detects the OS, installs the appropriate LSP binary, and writes the configuration (user-level or repo-level) in the format Copilot CLI expects.

Generated from the current SKILL.md.

Does this configure LSP for my editor or IDE?
No. This skill configures LSP servers specifically for Copilot CLI, not for VS Code, Neovim, or other editors. Use it when you need code intelligence features (go-to-definition, find-references, hover) within the Copilot CLI workflow.
What happens if my language isn't in the reference file?
The skill searches the web for a suitable LSP server for that language and guides you through manual configuration with the JSON format.
Can I have multiple language servers configured at once?
Yes. The JSON structure supports multiple servers in the same `lspServers` object, and the skill merges new entries without overwriting existing ones.
Do I need to restart Copilot CLI after setup?
Yes. You must type `/exit` to quit Copilot CLI so the new LSP configuration is loaded on the next launch.
Can I use both user-level and repo-level LSP config?
Yes. Repo-level config takes precedence over user-level, so you can set defaults at user-level and override them per repository.

Generated from the current SKILL.md. These answers refresh after source changes.