Cursor Skill

rust-call-graph

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

LLM Mart · 0 points · 9 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download moeru-ai-auv-.agents_skills_rust-call-graph-372a07b.zip · 1 KB
moeru-ai/auv 51 6 forks Apache-2.0 Updated 14h ago
Part of moeru-ai/auv — 28 skills

Install

skills CLI npx skills add https://github.com/moeru-ai/auv/tree/main/.agents/skills/rust-call-graph
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install moeru-ai-auv@llmmart
Git git clone https://github.com/moeru-ai/auv.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole moeru-ai/auv collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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
Files (auv)
  • SKILL.md 5.5 KB
    ---
    name: rust-call-graph
    description: "Visualize Rust function call graphs using LSP. Triggers on: /call-graph, call hierarchy, who calls, what calls, 调用图, 调用关系, 谁调用了, 调用了谁"
    argument-hint: "<function_name> [--depth N] [--direction in|out|both]"
    allowed-tools: ["LSP", "Read", "Glob"]
    ---
    
    # 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
    
    ```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
    ```
    
    ## Related Skills
    
    | When | See |
    |------|-----|
    | Find definition | rust-code-navigator |
    | Project structure | rust-symbol-analyzer |
    | Trait implementations | rust-trait-explorer |
    | Safe refactoring | rust-refactor-helper |
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related