fireauto-lsp-guide

Prioritize LSP operations for code navigation with fallbacks to Glob/Grep and Read.

139|35|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/imgompanda/fireauto --skill fireauto-lsp-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fireauto-lsp-guide
Source: https://github.com/imgompanda/fireauto/tree/main/plugin/skills/fireauto-lsp-guide
Command: npx skills add https://github.com/imgompanda/fireauto --skill fireauto-lsp-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working on large codebases, developers waste time chasing definitions and references using basic search; this skill guides you to consistently use LSP for code navigation to accelerate understanding.

Core Features & Use Cases

  • LSP-first navigation: goToDefinition, findReferences, hover, documentSymbol, and workspaceSymbol are prioritized.
  • Fall back strategy: if LSP is unavailable or incomplete, glob/grep searches are used, then content is read for verification.
  • Use cases: quickly locate where a function is defined, where it is used, and what its type and interfaces are across modules.

Quick Start

Enable LSP-first navigation and start using goToDefinition and findReferences for code exploration.

Frequently Asked Questions about fireauto-lsp-guide

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

FAQPage Schema
How do I use LSP for code navigation to find definitions and references?

Use LSP for code navigation by prioritizing operations like goToDefinition and findReferences to quickly locate function definitions and usages. This accelerates codebase understanding across multiple languages.

What is the best way to locate symbols across a multi-language codebase?

The best way to locate symbols in a multi-language codebase is using LSP-first navigation. Prioritize workspaceSymbol and documentSymbol operations to accurately find type and interface information across modules.

What should I do when LSP is unavailable or returns incomplete results?

When LSP is unavailable or incomplete, fall back to glob and grep searches to find text matches, then read the file content directly to verify the definition or reference locations.

Can I trace incoming and outgoing calls using LSP instead of basic text search?

Yes, you can trace incoming and outgoing calls using LSP operations instead of basic text search. LSP provides accurate call hierarchy tracking, ensuring you find exact function invocations across modules.

Why does using LSP accelerate code understanding compared to grep?

Using LSP accelerates code understanding because it provides semantic awareness, accurately distinguishing between definitions, references, and implementations, whereas grep only matches text patterns blindly.