rust-code-navigator

Navigate large Rust codebases efficiently using Language Server Protocol.

actionbook/rust-skillsUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

980

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/actionbook/rust-skills --skill rust-code-navigator

0

installs

0

this week

980

stars

Installation Guide

How to use rust-code-navigator on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add rust-code-navigator
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/actionbook/rust-skills --skill rust-code-navigator

Fetches rust-code-navigator from actionbook/rust-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/rust-code-navigator

Restart Cursor to activate rust-code-navigator. Access via /rust-code-navigator in your agent's command palette.

Security Notice

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.

Documentation

Rust Code Navigator

Navigate large Rust codebases efficiently using Language Server Protocol.

Usage

/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 location

LSP Operations

1. Go to Definition

Find where a symbol is defined.

LSP(
  operation: "goToDefinition",
  filePath: "src/main.rs",
  line: 25,
  character: 10
)

Use when:

  • User asks "where is X defined?"
  • User wants to understand a type/function
  • Ctrl+click equivalent

2. Find References

Find all usages of a symbol.

LSP(
  operation: "findReferences",
  filePath: "src/lib.rs",
  line: 15,
  character: 8
)

Use when:

  • User asks "who uses X?"
  • Before refactoring/renaming
  • Understanding impact of changes

3. Hover Information

Get type and documentation for a symbol.

LSP(
  operation: "hover",
  filePath: "src/main.rs",
  line: 30,
  character: 15
)

Use when:

  • User asks "what type is X?"
  • User wants documentation
  • Quick type checking

Workflow

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

Output Format

Definition Found

## 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 Found

## 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>` |

Common Patterns

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 Handling

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

Related Skills

When See
Call relationships rust-call-graph
Project structure rust-symbol-analyzer
Trait implementations rust-trait-explorer
Safe refactoring rust-refactor-helper

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Steps

  1. 1Install skill using provided installation command
  2. 2Test with simple use case relevant to your work
  3. 3Evaluate output quality and relevance
  4. 4Iterate on prompts to improve results
  5. 5Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ 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.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Related Skills

Reviews

4.440 reviews
  • D
    Dhruvi JainDec 28, 2024

    Solid pick for teams standardizing on skills: rust-code-navigator is focused, and the summary matches what you get after install.

  • T
    Tariq ReddyDec 24, 2024

    Registry listing for rust-code-navigator matched our evaluation — installs cleanly and behaves as described in the markdown.

  • K
    Kaira NdlovuDec 24, 2024

    Solid pick for teams standardizing on skills: rust-code-navigator is focused, and the summary matches what you get after install.

  • O
    OshnikdeepNov 19, 2024

    We added rust-code-navigator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • J
    James ParkNov 15, 2024

    Useful defaults in rust-code-navigator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • K
    Kaira ParkNov 15, 2024

    We added rust-code-navigator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • L
    Li ReddyNov 7, 2024

    Keeps context tight: rust-code-navigator is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Z
    Zara RahmanOct 26, 2024

    rust-code-navigator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • G
    Ganesh MohaneOct 10, 2024

    rust-code-navigator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • M
    Mei SinghOct 6, 2024

    I recommend rust-code-navigator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 40

1 / 4

Discussion

Comments — not star reviews
  • No comments yet — start the thread.