rysweet LSP Setup Skill
Purpose
Help users enable or troubleshoot language-server-backed code intelligence. This skill uses installed language servers, editor/agent integration, repository conventions, and a bundled native status helper.
Workflow
- Detect project languages from manifests and source files.
- Check whether a suitable language server is already available on
PATH. - Prefer existing project setup instructions and package-manager scripts.
- For missing servers, recommend the ecosystem-standard install command for the detected language.
- Verify by running the language server's status/version command or by exercising available code-intelligence tools.
Native Helper
amplifier-bundle/skills/lsp-setup/scripts/lsp-setup.sh status
amplifier-bundle/skills/lsp-setup/scripts/lsp-setup.sh recommend
The helper detects common project languages, checks language-server availability on PATH, and prints ecosystem-standard install hints.
Common Servers
| Language | Server |
|---|---|
| Rust | rust-analyzer |
| Go | gopls |
| TypeScript/JavaScript | TypeScript language server |
| C#/.NET | Roslyn / C# Dev Kit server |
| Java | Eclipse JDT LS |
Python projects may use Pyright or basedpyright when the repository already uses that ecosystem; this is language support, not an amplihack runtime dependency.
Failure Handling
If LSP setup is unavailable, state that explicitly and fall back to static analysis with rg, build metadata, and existing tests. Do not claim LSP-assisted results when only static analysis was used.