rust-call-graph

zhanghandong/rust-skills · updated Apr 8, 2026

$npx skills add https://github.com/zhanghandong/rust-skills --skill rust-call-graph
0 commentsdiscussion
summary

Visualize Rust function call graphs with configurable depth and direction using LSP.

  • Supports three query directions: incoming calls (who calls this), outgoing calls (what this calls), and bidirectional analysis
  • Configurable traversal depth (default 3 levels) to control graph scope and complexity
  • Generates ASCII tree visualizations with entry points, leaf functions, and hot path analysis
  • Includes complexity insights and potential issues flagging (high fan-out, multiple callers)
skill.md

Rust Call Graph

Visualize function call relationships using LSP call hierarchy.

Usage

/rust-call-graph <function_name> [--depth N] [--direction in|out|both]

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.

LSP(
  operation: "prepareCallHierarchy",
  filePath: "src/handler.rs",
  line: 45,
  character: 8
)

2. Incoming Calls (Who calls this?)

LSP(
  operation: "incomingCalls",
  filePath: "src/handler.rs",
  line: 45,
  character: 8
)

3. Outgoing Calls (What does this call?)

LSP(
  operation: "outgoingCalls",
  filePath: "src/handler.rs",
  line: 45,
  character: 8
)

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

Output Format

Incoming Calls (Who calls this?)

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

Bidirectional (Both)

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

Common Patterns

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

Visualization Options

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

Mermaid Export

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

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

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.749 reviews
  • Chen Gupta· Dec 28, 2024

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

  • Alexander Menon· Dec 24, 2024

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

  • Ganesh Mohane· Dec 4, 2024

    rust-call-graph has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Rahul Santra· Nov 23, 2024

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

  • James Huang· Nov 19, 2024

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

  • Ishan Srinivasan· Nov 15, 2024

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

  • Pratham Ware· Oct 14, 2024

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

  • James Khan· Oct 10, 2024

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

  • James Singh· Oct 6, 2024

    rust-call-graph has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yusuf Huang· Sep 17, 2024

    rust-call-graph reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 49

1 / 5