lsp-setup

Configure language servers for diagnostics and navigation in Codex or OpenCode projects.

5|Updated May 17, 2026
One-click install
npx skills add https://github.com/islee23520/lfg --skill lsp-setup-islee23520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lsp-setup
Source: https://github.com/islee23520/lfg/tree/main/skills/lsp-setup
Command: npx skills add https://github.com/islee23520/lfg --skill lsp-setup-islee23520

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the guesswork from configuring language servers so diagnostics, go-to-definition, find-references, rename, and symbol navigation work reliably in your editor or agent tools.

Core Features & Use Cases

  • Detects the language in a project and points you to the correct builtin server and installation path.
  • Helps you choose between competing servers, write the right project or user configuration, and set priority or initialization options when needed.
  • Verifies the setup with a real diagnostics roundtrip and gives practical troubleshooting guidance when a server is missing, misconfigured, or not matching the project environment.

Quick Start

Ask the skill to set up LSP support for your project, and it will identify the languages present, recommend the right servers, write the configuration, and confirm that diagnostics work.

Frequently Asked Questions about lsp-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a language server for diagnostics and code navigation?

To configure a language server for diagnostics and code navigation, you need a JSON configuration file like .codex/lsp-client.json or .opencode/lsp.json. The setup process identifies your project languages, recommends builtin servers, and verifies diagnostics work through a roundtrip test.

How do I set up LSP support for a multi-language project?

Setting up LSP support for a multi-language project involves detecting the languages present and selecting the correct builtin server for each. You will need per-language installation guidance and project-scoped configuration to ensure diagnostics, rename, and reference lookup work reliably.

What is the best way to troubleshoot language server issues when go-to-definition is not working?

The best way to troubleshoot language server issues when go-to-definition is not working is to run a real diagnostics verification roundtrip. This process identifies if a server is missing, misconfigured, or not matching the project environment.

Does LSP setup work with Codex or OpenCode agent workflows?

Yes, LSP setup works with Codex or OpenCode agent workflows by utilizing project-scoped JSON configuration files. Configuring the language server correctly ensures diagnostics and symbol navigation function reliably within these agent tools.

Why does my language server not match my project environment?

Your language server might not match your project environment due to missing OS-specific install commands or incorrect initialization options. Troubleshooting this requires verifying the server installation and checking the project or user configuration priority.

Do I need to install separate language servers for find-references and rename to work?

You need the correct builtin language server installed for find-references and rename to work. The setup process provides OS-specific installation commands and points you to the right server so these navigation features function correctly.