rust-call-graph

Generates ASCII call graphs showing caller–calle relationships for Rust functions via LSP call hierarchy endpoints.

1|2|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/dojoengine/torii-core --skill rust-call-graph-dojoengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-call-graph
Source: https://github.com/dojoengine/torii-core/tree/main/.agents/skills/rust-call-graph
Command: npx skills add https://github.com/dojoengine/torii-core --skill rust-call-graph-dojoengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understand Rust function call relationships to help debugging, code comprehension, and performance analysis.

Core Features & Use Cases

  • Visualize incoming and outgoing calls for a symbol.
  • Explore prepareCallHierarchy and recursively expand callers and callees.
  • Use ASCII visualizations to communicate call graphs in documentation or reviews.

Quick Start

Run the rust-call-graph command with a function name to visualize its call graph.

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 for a specific function?

You can visualize a Rust call graph by running the rust-call-graph command with a function name, which uses LSP operations like prepareCallHierarchy to map caller-callee relationships and render them as ASCII visualizations.

What is the best way to understand incoming and outgoing Rust function calls for debugging?

To understand incoming and outgoing Rust function calls for debugging, use this Skill to recursively expand callers and callees via LSP, producing an interactive call graph that clearly reveals caller-callee relationships for the target symbol.

Can I generate ASCII call graph visualizations for Rust code reviews?

Yes, you can generate ASCII call graph visualizations for Rust code to communicate caller-callee relationships directly in documentation, code reviews, or refactoring plans.

Does this Rust call graph tool require an existing LSP setup?

The tool integrates with LSP operations such as prepareCallHierarchy, incomingCalls, and outgoingCalls to extract function relationships, so your Rust project should be compatible with LSP-powered static analysis.

When do I need to visualize caller-callee relationships in a Rust project?

You need to visualize caller-callee relationships in a Rust project when you are debugging complex code flow, analyzing performance bottlenecks, or planning a refactoring effort across interconnected functions.

Are there limitations to using static analysis for Rust code navigation?

Static analysis for Rust code navigation relies on LSP prepareCallHierarchy data, so dynamic dispatch and trait object calls may not fully resolve in the resulting ASCII call graph visualizations.