Navigate Rust code using Language Server Protocol for definitions, references, and symbol information.
Works with
Supports three core LSP operations: go to definition, find references, and hover information for type/documentation lookup
Handles workspace symbol search with disambiguation when multiple results exist, plus file-specific navigation with line numbers
Includes error handling for missing rust-analyzer, typos, and generics/macros that produce multiple definitions
Output formatted a
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrust-code-navigatorExecute the skills CLI command in your project's root directory to begin installation:
Fetches rust-code-navigator from zhanghandong/rust-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate rust-code-navigator. Access via /rust-code-navigator in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
979
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
979
stars
Navigate large Rust codebases efficiently using Language Server Protocol.
/rust-code-navigator <symbol> [in file.rs:line]
Examples:
/rust-code-navigator parse_config - Find definition of parse_config/rust-code-navigator MyStruct in src/lib.rs:42 - Navigate from specific locationFind where a symbol is defined.
LSP(
operation: "goToDefinition",
filePath: "src/main.rs",
line: 25,
character: 10
)
Use when:
Find all usages of a symbol.
LSP(
operation: "findReferences",
filePath: "src/lib.rs",
line: 15,
character: 8
)
Use when:
Get type and documentation for a symbol.
LSP(
operation: "hover",
filePath: "src/main.rs",
line: 30,
character: 15
)
Use when:
User: "Where is the Config struct defined?"
│
▼
[1] Search for "Config" in workspace
LSP(operation: "workspaceSymbol", ...)
│
▼
[2] If multiple results, ask user to clarify
│
▼
[3] Go to definition
LSP(operation: "goToDefinition", ...)
│
▼
[4] Show file path and context
Read surrounding code for context
## Config (struct)
**Defined in:** `src/config.rs:15`
```rust
#[derive(Debug, Clone)]
pub struct Config {
pub name: String,
pub port: u16,
pub debug: bool,
}
```
**Documentation:** Configuration for the application server.
## References to `Config` (5 found)
| Location | Context |
|----------|---------|
| src/main.rs:10 | `let config = Config::load()?;` |
| src/server.rs:25 | `fn new(config: Config) -> Self` |
| src/server.rs:42 | `self.config.port` |
| src/tests.rs:15 | `Config::default()` |
| src/cli.rs:8 | `config: Option<Config>` |
| User Says | LSP Operation |
|---|---|
| "Where is X defined?" | goToDefinition |
| "Who uses X?" | findReferences |
| "What type is X?" | hover |
| "Find all structs" | workspaceSymbol |
| "What's in this file?" | documentSymbol |
| Error | Cause | Solution |
|---|---|---|
| "No LSP server" | rust-analyzer not running | Suggest: rustup component add rust-analyzer |
| "Symbol not found" | Typo or not in scope | Search with workspaceSymbol first |
| "Multiple definitions" | Generics or macros | Show all and let user choose |
| When | See |
|---|---|
| Call relationships | rust-call-graph |
| Project structure | rust-symbol-analyzer |
| Trait implementations | rust-trait-explorer |
| Safe refactoring | rust-refactor-helper |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
wispbit-ai/skills
asyrafhussin/agent-skills
shadcn/improve
kunchenguid/no-mistakes
simonwong/agent-skills
awesome-skills/code-review-skill
rust-code-navigator reduced setup friction for our internal harness; good balance of opinion and flexibility.
rust-code-navigator has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: rust-code-navigator is focused, and the summary matches what you get after install.
rust-code-navigator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added rust-code-navigator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
rust-code-navigator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
rust-code-navigator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: rust-code-navigator is focused, and the summary matches what you get after install.
I recommend rust-code-navigator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
rust-code-navigator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 41