rust-code-navigator

Locate Rust symbols and definitions using rust-analyzer LSP queries.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill rust-code-navigator-jmduea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-code-navigator
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/rust-code-navigator
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill rust-code-navigator-jmduea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigating large Rust codebases and finding definitions, references, or type information is time‑consuming without tooling.

Core Features & Use Cases

  • Go to Definition: Quickly jump to where a function, struct, or trait is defined.
  • Find References: List all usages of a symbol across the workspace, aiding refactoring.
  • Hover Information: Retrieve type signatures and documentation for any symbol.
  • Workspace Symbol Search: Locate symbols by name throughout the project.

Use cases include debugging, exploring unfamiliar code, and reviewing call sites.

Quick Start

Ask the assistant, “Where is the Config struct defined?”

Frequently Asked Questions about rust-code-navigator

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

FAQPage Schema
How do I find all references to a Rust symbol across my codebase?

To find Rust references, you use this tool to list all usages of a symbol across the workspace via the rust-analyzer LSP server. It requires an active LSP server and file paths to resolve symbols.

Can I retrieve type signatures and documentation for Rust code via LSP?

Yes, you can retrieve type signatures and documentation for Rust code by triggering hover queries. This functionality requires an active rust-analyzer LSP server to provide hover information for any symbol in your project.

What is the best way to locate Rust struct definitions in a large codebase?

The best way to locate Rust definitions in a large codebase is using go-to-definition queries through an active rust-analyzer LSP server. You can instantly jump to where a function, struct, or trait is defined by providing file paths.

Does this code-navigation approach require an active rust-analyzer LSP server?

Yes, this code-navigation approach requires an active rust-analyzer LSP server. It relies entirely on the LSP server and file paths to resolve symbols, handle go-to-definition, find-references, and hover queries across files.

When do I need to use LSP for workspace symbol search in Rust projects?

You need to use LSP for workspace symbol search in Rust projects when exploring unfamiliar code or debugging. It allows you to locate symbols by name throughout the project, instantly retrieving definitions and references across files.