rust-symbol-analyzer

Index and structure Rust symbols via LSP document and workspace queries.

1.4k|110|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/actionbook/rust-skills --skill rust-symbol-analyzer-actionbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-symbol-analyzer
Source: https://github.com/actionbook/rust-skills/tree/main/skills/rust-symbol-analyzer
Command: npx skills add https://github.com/actionbook/rust-skills --skill rust-symbol-analyzer-actionbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes Rust codebases by extracting and organizing symbols to reveal architecture, modules, and relationships.

Core Features & Use Cases

  • Symbol extraction: Enumerates modules, structs, traits, and functions across the workspace using LSP.
  • Visualized structure: Generates a hierarchical view of project layout to assist navigation.
  • Use Case: Quickly assess a large Rust repo to understand module boundaries and API surface.

Quick Start

/rust-symbol-analyzer [file.rs] [--type struct|trait|fn|mod]

Frequently Asked Questions about rust-symbol-analyzer

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

FAQPage Schema
How do I analyze Rust project structure and extract symbols?

Analyze Rust project structure by indexing and structuring symbols via LSP, extracting modules, structs, traits, and functions to generate a hierarchical view of the codebase organization and API surface.

How does LSP workspaceSymbol enumerate Rust modules and traits?

LSP workspaceSymbol queries enumerate Rust modules and traits across the entire workspace, while documentSymbol operations extract symbols from single files, producing a structured hierarchical project layout for code navigation.

Can I filter Rust symbols by type to list only structs or functions?

Filter Rust symbols by type using the --type flag with struct, trait, fn, or mod arguments, enabling type-filtered symbol listings to inspect specific code constructs within the workspace.

What's the best way to navigate a large Rust codebase and understand module boundaries?

Navigate large Rust codebases by generating a hierarchical view of project layout from LSP symbol extraction, assessing module boundaries and API surface to quickly understand code organization and architecture.

Do I need LSP to inspect Rust code organization and single-file symbols?

LSP is required to inspect Rust code organization, as the analyzer relies on LSP documentSymbol and workspaceSymbol operations to produce hierarchical views of symbols for both single-file inspection and whole-workspace analysis.

Why use LSP documentSymbol for Rust codebase navigation instead of manual inspection?

LSP documentSymbol provides structured symbol extraction for Rust files, revealing module boundaries and relationships automatically, whereas manual inspection lacks the hierarchical organization needed to understand complex project architecture efficiently.