Labsco
github logo

lsp-setup

✓ Official★ 36,200

by github · part of github/awesome-copilot

Enable code intelligence (go-to-definition, find-references, hover, type info) for any programming language by installing and configuring an LSP server for…

🔥🔥🔥🔥✓ VerifiedFreeQuick setup
#automation#git#maps
🧩 One of 7 skills in the github/awesome-copilot package — works on its own, and pairs well with its siblings.

Enable code intelligence (go-to-definition, find-references, hover, type info) for any programming language by installing and configuring an LSP server for…

Inspect the full instructions your agent will receiveExpand

This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.

by github

Enable code intelligence (go-to-definition, find-references, hover, type info) for any programming language by installing and configuring an LSP server for… npx skills add https://github.com/github/awesome-copilot --skill lsp-setup Download ZIPGitHub36.2k

Workflow

  • Ask the language — use ask_user to ask which programming language(s) the user wants LSP support for

  • Detect the OS — run uname -s (or check for Windows via $env:OS / %OS%) to determine macOS, Linux, or Windows

  • Look up the LSP server — read references/lsp-servers.md for known servers, install commands, and config snippets

  • Ask scope — use ask_user to ask whether the config should be user-level (~/.copilot/lsp-config.json) or repo-level (lsp.json at the repo root or .github/lsp.json)

  • Install the server — run the appropriate install command for the detected OS

  • Write the config — merge the new server entry into the chosen config file (~/.copilot/lsp-config.json for user-level; lsp.json or .github/lsp.json for repo-level). If a repo-level config already exists, keep using that location; otherwise ask the user which repo-level location they prefer. Create the file if missing and preserve existing entries.

  • Verify — confirm the LSP binary is on $PATH and the config file is valid JSON

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 " 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:

  • Type /exit to quit Copilot CLI — this is required so the new LSP configuration is loaded on next launch

  • Re-launch copilot in a project with files of the configured language

  • Run /lsp to check the server status

  • Try code intelligence features like go-to-definition or hover