using-lsp-tools

Provides semantic navigation and accurate extraction of text, tables, and metadata from PDF files.

8|5|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill using-lsp-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-lsp-tools
Source: https://github.com/axiomantic/spellbook/tree/main/skills/using-lsp-tools
Command: npx skills add https://github.com/axiomantic/spellbook --skill using-lsp-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigate codebases and perform accurate refactoring when semantic understanding is required, by leveraging LSP tooling rather than simple text search.

Core Features & Use Cases

  • Semantic navigation: jump to definitions, references, types, and symbol hierarchies across files.
  • Safe refactoring: perform rename_symbol and code actions with cross-file impact awareness.
  • Type and symbol analysis: understand inheritance, interfaces, and usage patterns for maintainability across languages with LSP support.

Quick Start

Activate an LSP-enabled workspace and run a definition or reference query for a target symbol to navigate to its definition.

Frequently Asked Questions about using-lsp-tools

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

FAQPage Schema
How do I jump to definitions and references across multiple files in a codebase?

Semantic code navigation uses language server protocols to jump to definitions, references, and type information across multiple files. It requires an active LSP server and an accessible workspace to locate symbols accurately.

What is the best way to refactor symbols safely across an entire project?

Safe refactoring uses LSP tooling to perform rename_symbol and code actions with cross-file impact awareness. This ensures symbolic renames and code modifications propagate correctly throughout the workspace without breaking references.

Do I need an active language server to query type information and inheritance hierarchies?

Yes, an active language server is required. Type and symbol analysis queries for inheritance, interfaces, and usage patterns rely on an active LSP server to provide semantic understanding of the codebase.

Can I use semantic code navigation for any programming language in my workspace?

Semantic code navigation applies across languages with active LSP support. You can query definitions and references for any language in your workspace that has a compatible language server running.

Why use LSP tooling instead of simple text search to find code references?

LSP tooling provides semantic understanding rather than simple text search matching. It locates actual definitions, references, and type information, preventing false positives from string matches and ensuring accurate cross-file refactoring.

What are the limitations of using language server protocols for code refactoring?

LSP refactoring requires an active LSP server, an accessible workspace, and language support for code actions and symbolic renames. Without these prerequisites, cross-file refactoring and semantic navigation will not function.