lsp

Check workspace code with language-server tooling for diagnostics and refactoring.

5|Updated May 17, 2026

Search Tags:#code navigation #diagnostics #lsp #rename safety #workspace refactoring

Ready to run

npx skills add https://github.com/islee23520/lfg --skill lsp-islee23520

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lsp
Source: https://github.com/islee23520/lfg/tree/main/skills/lsp
Command: npx skills add https://github.com/islee23520/lfg --skill lsp-islee23520

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes guesswork from code editing by letting you inspect diagnostics, jump to definitions, find references, and verify renames with language-server support.

Core Features & Use Cases

Diagnostics: Check files or directories for errors after making changes.
Navigation: Jump to symbol definitions and inspect references across the workspace.
Refactoring Safety: Validate a rename before applying it, reducing broken links and missed updates.
Use Case: A developer refactors a function and uses this Skill to confirm that every reference, definition, and rename remains consistent.

Quick Start

Ask the LSP skill to inspect the current workspace for diagnostics, definitions, references, symbols, or rename safety before you edit code.

Frequently Asked Questions about lsp

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

FAQPage Schema

How do I check workspace code for errors after making changes?▼

You can check workspace code for errors by requesting diagnostics on specific files or directories to identify issues and validate your recent edits.

What is the best way to verify a function rename is safe across a workspace?▼

The best way to verify a function rename is safe is to run a prepare-rename check first, which validates that every reference and definition remains consistent before applying the change.

How does cross-file code navigation work when looking up symbol definitions?▼

Cross-file code navigation works by using language-server tooling to jump directly to symbol definitions and inspect references across the entire active workspace.

Do I need configured language servers to use LSP tools for refactoring?▼

Yes, you need configured language servers exposed through LSP MCP tools to perform refactoring verification, status checks, diagnostics, and reference search.

Can I search for references across the workspace before modifying code?▼

Yes, you can search for references across the workspace to inspect all usages of a symbol before modifying code, ensuring your edits do not break existing links.

When should I not rely on language-server tooling for code navigation?▼

You should not rely on language-server tooling when your workspace lacks configured language servers exposed through LSP MCP tools, as the skill requires them to function.