Rust Call Graph

by actionbook5c40d3ad7851No license1.5K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 weeks ago

Visualize Rust function call graphs using LSP. Triggers on: /call-graph, call hierarchy, who calls, what calls, 调用图, 调用关系, 谁调用了, 调用了谁

Instructions onlySoftware Development

AI-generated overview

Visualizes Rust function call graphs using LSP call hierarchy, showing callers, callees, and analysis insights.

What it does: This skill uses LSP call hierarchy operations to map Rust function call relationships. It prepares a call hierarchy for a target function, then retrieves incoming calls (callers) and outgoing calls (callees), recursively expanding to a configurable depth. It produces ASCII tree or box-diagram visualizations, optional Mermaid export, and analysis notes such as entry points, leaf functions, hot paths, and potential issues.
When to use it: Use it when you need to understand who calls a Rust function or what a function calls, for impact analysis, implementation understanding, or tracing execution paths. It fits questions like "who calls X?", "what does X call?", or "show the call graph".
Requirements: Requires an LSP-capable environment with call hierarchy support for Rust, plus Read and Glob tools. No scripts are shipped; it is instructions only.

Rust Call Graph

Visualize function call relationships using LSP call hierarchy.

Usage

Options:

--depth N: How many levels to traverse (default: 3)
--direction: in (callers), out (callees), both

Examples:

/rust-call-graph process_request - Show both callers and callees
/rust-call-graph handle_error --direction in - Show only callers
/rust-call-graph main --direction out --depth 5 - Deep callee analysis

LSP Operations

1. Prepare Call Hierarchy

Get the call hierarchy item for a function.

2. Incoming Calls (Who calls this?)

3. Outgoing Calls (What does this call?)

Workflow

User: "Show call graph for process_request"    │    ▼[1] Find function location    LSP(workspaceSymbol) or Grep    │    ▼[2] Prepare call hierarchy    LSP(prepareCallHierarchy)    │    ▼[3] Get incoming calls (callers)    LSP(incomingCalls)    │    ▼[4] Get outgoing calls (callees)    LSP(outgoingCalls)    │    ▼[5] Recursively expand to depth N    │    ▼[6] Generate ASCII visualization

User: "Show call graph for process_request"    │    ▼[1] Find function location    LSP(workspaceSymbol) or Grep    │    ▼[2] Prepare call hierarchy    LSP(prepareCallHierarchy)    │    ▼[3] Get incoming calls (callers)    LSP(incomingCalls)    │    ▼[4] Get outgoing calls (callees)    LSP(outgoingCalls)    │    ▼[5] Recursively expand to depth N    │    ▼[6] Generate ASCII visualization

Output Format

Incoming Calls (Who calls this?)

## Callers of `process_request`
main└── run_server    └── handle_connection        └── process_request  ◄── YOU ARE HERE

## Callers of `process_request`
main└── run_server    └── handle_connection        └── process_request  ◄── YOU ARE HERE

Outgoing Calls (What does this call?)

## Callees of `process_request`
process_request  ◄── YOU ARE HERE├── parse_headers│   └── validate_header├── authenticate│   ├── check_token│   └── load_user├── execute_handler│   └── [dynamic dispatch]└── send_response    └── serialize_body

## Callees of `process_request`
process_request  ◄── YOU ARE HERE├── parse_headers│   └── validate_header├── authenticate│   ├── check_token│   └── load_user├── execute_handler│   └── [dynamic dispatch]└── send_response    └── serialize_body

Bidirectional (Both)

## Call Graph for `process_request`
                    ┌─────────────────┐                    │      main       │                    └────────┬────────┘                             │                    ┌────────▼────────┐                    │   run_server    │                    └────────┬────────┘                             │                    ┌────────▼────────┐                    │handle_connection│                    └────────┬────────┘                             │        ┌────────────────────┼────────────────────┐        │                    │                    │┌───────▼───────┐   ┌───────▼───────┐   ┌───────▼───────┐│ parse_headers │   │ authenticate  │   │send_response  │└───────────────┘   └───────┬───────┘   └───────────────┘                            │                    ┌───────┴───────┐                    │               │             ┌──────▼──────┐ ┌──────▼──────┐             │ check_token │ │  load_user  │             └─────────────┘ └─────────────┘

## Call Graph for `process_request`
                    ┌─────────────────┐                    │      main       │                    └────────┬────────┘                             │                    ┌────────▼────────┐                    │   run_server    │                    └────────┬────────┘                             │                    ┌────────▼────────┐                    │handle_connection│                    └────────┬────────┘                             │        ┌────────────────────┼────────────────────┐        │                    │                    │┌───────▼───────┐   ┌───────▼───────┐   ┌───────▼───────┐│ parse_headers │   │ authenticate  │   │send_response  │└───────────────┘   └───────┬───────┘   └───────────────┘                            │                    ┌───────┴───────┐                    │               │             ┌──────▼──────┐ ┌──────▼──────┐             │ check_token │ │  load_user  │             └─────────────┘ └─────────────┘

Analysis Insights

After generating the call graph, provide insights:

## Analysis
**Entry Points:** main, test_process_request**Leaf Functions:** validate_header, serialize_body**Hot Path:** main → run_server → handle_connection → process_request**Complexity:** 12 functions, 3 levels deep
**Potential Issues:**- `authenticate` has high fan-out (4 callees)- `process_request` is called from 3 places (consider if this is intentional)

## Analysis
**Entry Points:** main, test_process_request**Leaf Functions:** validate_header, serialize_body**Hot Path:** main → run_server → handle_connection → process_request**Complexity:** 12 functions, 3 levels deep
**Potential Issues:**- `authenticate` has high fan-out (4 callees)- `process_request` is called from 3 places (consider if this is intentional)

Common Patterns

Visualization Options

Mermaid Export

mermaid

graph TD    main --> run_server    run_server --> handle_connection    handle_connection --> process_request    process_request --> parse_headers    process_request --> authenticate    process_request --> send_response

graph TD    main --> run_server    run_server --> handle_connection    handle_connection --> process_request    process_request --> parse_headers    process_request --> authenticate    process_request --> send_response

Related Skills

Source and attribution

Source:actionbook/rust-skillsinskills/rust-call-graphat commit5c40d3a

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

User Says	Direction	Use Case
"Who calls X?"	incoming	Impact analysis
"What does X call?"	outgoing	Understanding implementation
"Show call graph"	both	Full picture
"Trace from main to X"	outgoing	Execution path

Style	Best For
Tree (default)	Simple hierarchies
Box diagram	Complex relationships
Flat list	Many connections
Mermaid	Export to docs

When	See
Find definition	rust-code-navigator
Project structure	rust-symbol-analyzer
Trait implementations	rust-trait-explorer
Safe refactoring	rust-refactor-helper

Rust Call Graph

Rust Call Graph

Usage

LSP Operations

1. Prepare Call Hierarchy

2. Incoming Calls (Who calls this?)

3. Outgoing Calls (What does this call?)

Workflow

Output Format

Incoming Calls (Who calls this?)

Outgoing Calls (What does this call?)

Bidirectional (Both)

Analysis Insights

Common Patterns

Visualization Options

Mermaid Export

Related Skills

Source and attribution

More from actionbook/rust-skills

Rust Trait Explorer

Rust Symbol Analyzer

Rust Skill Creator

Rust Router

Rust Refactor Helper

Rust Daily

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices