using-code-navigation

Navigate and refactor code symbols using LSP-backed semantic tools instead of grep.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill using-code-navigation-danielsuguimoto
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: using-code-navigation
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/using-code-navigation
Command: npx skills add https://github.com/danielsuguimoto/skills --skill using-code-navigation-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Grep and plain file reads are slow and inaccurate for symbol-level code work like finding where a method is defined, who calls it, or safely renaming it across a codebase. This Skill routes those tasks to LSP-backed code navigation tools that return precise, token-efficient results. ## Core Features & Use Cases - Symbol Lookup and Navigation: Find classes, methods, and functions by name path, get symbol overviews of unfamiliar files, and locate declarations, references, and implementations. - Safe Refactoring: Rename symbols across the codebase with LSP-aware updates, safely delete symbols after checking references, and verify edits with per-file diagnostics. - Project Memory: Persist per-project markdown notes (onboarding findings, architecture decisions) and recall them in later sessions. - Use Case: When tracing a bug through a call chain, find the entry-point symbol, list its referencing symbols, and repeat on each caller until you reach the controller or route boundary β€” all without reading entire files. ## Quick Start Activate the current project on the code navigation server, then find all references to the method UserService/authenticate.

Frequently Asked Questions about using-code-navigation

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

FAQPage Schema
How do I find all references to a method in a codebase?β–Ό

Use the find referencing symbols operation with the method's name_path (e.g. Class/method) and its relative_path from a prior find symbol result. This returns every caller via LSP, which is more accurate than text search.

How to rename a function across an entire project safely?β–Ό

Use the rename symbol operation, which performs an LSP-aware rename that updates all references automatically. Afterwards, run get diagnostics for file on touched files to confirm no errors were introduced.

When should I use LSP symbol tools instead of grep?β–Ό

Use symbol tools whenever you know the name of a class, method, or function and need definitions, references, or implementations. Use grep only for plain-text or regex searches, non-code files, or dynamic code the LSP cannot resolve.

Why does the code navigation tool return 'No active project'?β–Ό

Every code navigation tool requires an activated project first. Call activate project with the project folder name or full path at the start of each session, after changing working directories, then retry the failed call.

What are the limitations of LSP-based code navigation?β–Ό

The LSP must support the language, and dynamic or eval'd symbols, templates, and config arrays may not resolve β€” fall back to grep or read there. Line numbers are 0-based, and find references requires a file's relative_path, not a directory.