skills.rest
actionbook
actionbookOFFICIAL
Explore all skills by this author →
WebsiteGitHub

rust-call-graph

Visualize Rust function call graphs using LSP to reveal callers and callees.

1.4k|110|Updated Jan 17, 2026
Search Tags:#rust#lsp#call graph#callers#code-navigation#callees
One-click install
npx skills add https://github.com/actionbook/rust-skills --skill rust-call-graph-actionbook
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rust-call-graph
Source: https://github.com/actionbook/rust-skills/tree/main/skills/rust-call-graph
Command: npx skills add https://github.com/actionbook/rust-skills --skill rust-call-graph-actionbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill visualizes Rust function call graphs using LSP to reveal callers and callees, helping developers understand complex call relationships.

Core Features & Use Cases

  • LSP-based call graph visualization: Explore who calls whom within a Rust project.
  • Callees and Callers tracing: Navigate call hierarchy to identify hot paths.
  • Codebase onboarding and auditing: Useful for refactoring, debugging, and knowledge transfer.

Quick Start

To get started, run the rust-call-graph skill with a function name to generate a call graph, for example: /rust-call-graph process_request You can specify optional depth and direction with --depth N and --direction in|out|both.

Frequently Asked Questions about rust-call-graph

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

FAQPage Schema
How do I visualize a Rust call graph to trace function callers and callees?▼

You visualize a Rust call graph by using LSP tooling to map function callers and callees. This traces call relationships across modules and crates to reveal execution paths for debugging and refactoring.

What is the best way to navigate call hierarchy in a large Rust codebase?▼

Navigating call hierarchy in a large Rust codebase is done by generating an LSP-based call graph. It traces execution paths across modules, crates, and interfaces, making codebase onboarding and auditing highly efficient.

Do I need extra dependencies to trace Rust callees and callers across crates?▼

You do not need extra dependencies to trace Rust callees and callers across crates. It requires only standard LSP tooling, applying to Rust projects of any size to map cross-crate call relationships.

How do I limit the depth or direction when tracing a Rust function call graph?▼

You limit depth or direction when tracing a Rust function call graph by using optional parameters. Specify --depth N to control traversal levels and --direction in|out|both to focus on callers, callees, or both.

When should I use a Rust call graph for refactoring and debugging?▼

You should use a Rust call graph for refactoring and debugging when you need to understand complex call relationships. It helps identify hot paths, navigate call hierarchies, and transfer knowledge during codebase audits.

Related Skills

Explore More Software Engineering Skills→
tarrragontarrragon
1

lsp-first

Configure language servers and navigate code using LSP protocols.

Community
Intermediate
skogaiskogai

explore-codebase

Map codebase relationships between functions, classes, and modules using knowledge graph tools.

Official
Intermediate
Jaydpatel01Jaydpatel01

code-quality-and-review

Enforce code correctness, readability, and safety with linters and type checkers.

Community
Advanced
OrestesKOrestesK
2

code-intelligence

Trace symbol references, call hierarchies, and diagnostics across codebases.

Community
Advanced