Agent skill

Rust Call Graph

by fjrevoredo in fjrevoredo/mini-diarium

Visualize Rust function call graphs using LSP. An agent skill from fjrevoredo/mini-diarium.

MITAuto-check passedDevelopment

Install Rust Call Graph

skills CLI
$ npx skills add fjrevoredo/mini-diarium --skill rust-call-graph -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fjrevoredo/mini-diarium rust-call-graph --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fjrevoredo/mini-diarium.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/rust-call-graph .claude/skills/rust-call-graph && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rust-call-graph
GitHub stars
308
Used in
1 other repo
Token cost
~1.2k tokens
SKILL.md length
177 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
MIT

At a glance

Visualize Rust function call graphs using LSP. An agent skill from fjrevoredo/mini-diarium.

  • Works in 3 steps: Prepare Call Hierarchy → Incoming Calls (Who calls this?) → Outgoing Calls (What does this call?)
  • Tasks that involve Codebase onboarding
  • SKILL.md covers Usage, LSP Operations, Workflow and Output Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rust Call Graph is an agent skill from fjrevoredo/mini-diarium. Visualize Rust function call graphs using LSP. Triggers on: /call-graph, call hierarchy, who calls, what calls, 调用图, 调用关系, 谁调用了, 调用了谁

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Codebase onboarding and Incident response. It works with Rust. The repository describes itself as: A local-only journal with serious encryption. Free, open source, and never touches the internet. The licence is MIT.

When your agent uses it

  • Tasks that involve Codebase onboarding
  • Tasks that involve Incident response

Example prompts

  • “/rust-call-graph”

Requirements

  • Pre-approved tools (allowed-tools): LSP, Read, Glob

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Prepare Call Hierarchy
  2. Incoming Calls (Who calls this?)
  3. Outgoing Calls (What does this call?)

What it can do on your machine

Read from SKILL.md and the folder at commit 75c1286. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • LSP
    • Read
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rust Call Graph loads about 1.2k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 177 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fjrevoredo/mini-diarium at commit 75c1286, republished under its MIT licence (© fjrevoredo). 177 words, ~1,188 tokens.

Download SKILL.mdSave it as .claude/skills/rust-call-graph/SKILL.md (or your agent's skills folder).
name
rust-call-graph
description
Visualize Rust function call graphs using LSP. Triggers on: /call-graph, call hierarchy, who calls, what calls, 调用图, 调用关系, 谁调用了, 调用了谁
allowed-tools
LSP, Read, Glob
argument-hint
<function_name> [--depth N] [--direction in|out|both]

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 SaysDirectionUse Case
"Who calls X?"incomingImpact analysis
"What does X call?"outgoingUnderstanding implementation
"Show call graph"bothFull picture
"Trace from main to X"outgoingExecution path

Visualization Options

StyleBest For
Tree (default)Simple hierarchies
Box diagramComplex relationships
Flat listMany connections
MermaidExport 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
WhenSee
Find definitionrust-code-navigator
Project structurerust-symbol-analyzer
Trait implementationsrust-trait-explorer
Safe refactoringrust-refactor-helper

© fjrevoredo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/rust-call-graph of fjrevoredo/mini-diarium.

Open the folder on GitHubat commit 75c1286

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in fjrevoredo/mini-diarium, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Rust Call Graph next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rust Call Graph compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rust Call Graph this skillfjrevoredo/mini-diarium3081 repos~1.2kAutomated safety check: PassMIT
Deepwiki Rssopaco/deepwiki-rs3.1k—~748Automated safety check: PassMIT
tilth Code Reading CLIjahala/tilth352—~1.1kAutomated safety check: PassMIT
Project StructureEynzof/Hermes-CN-Desktop1.7k—~4.2kAutomated safety check: NotesCustom licence
Codex Proxy RS Development Guidezyycn/codex-proxy-rs738—~618Automated safety check: PassApache-2.0
Flowfile Build and Environment SetupEdwardvaneechoud/Flowfile370—~7.3kAutomated safety check: NotesMIT

Similar skills

  • Deepwiki Rs

    sopaco/deepwiki-rs

    AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation.

    3.1k GitHub stars~748 tokensUpdated 23 days ago
    DevelopmentAuto-check passed
  • Replaces grep, cat, find and ls with the tilth CLI, which returns AST-aware outlines, definitions, usages and callers across many languages in one call.

    352 GitHub stars~1.1k tokensUpdated 10 days ago
    DevelopmentAuto-check passed
  • Project Structure

    Eynzof/Hermes-CN-Desktop

    A skill your agent uses when orienting within the Hermes Agent CN Desktop codebase, locating source files, understanding the Tauri+React architecture, finding Rust commands or frontend modules, or…

    1.7k GitHub stars~4.2k tokensUpdated 16 days ago
    DevelopmentAuto-check: notes
  • Routes development, troubleshooting, review and documentation tasks on the Codex Proxy RS repository to the right section of its docs, instead of loading the whole architecture or contributing guide.

    738 GitHub stars~618 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Flowfile Build and Environment Setup

    Edwardvaneechoud/Flowfile

    Recreates every Flowfile development and build environment from scratch, with exact version pins and an explanation of what each Makefile target really does.

    370 GitHub stars~7.3k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Codewhale Contributor Onboarding

    codewhale-hq/Codewhale

    Reports whether a fresh Codewhale checkout is current, builds and passes its tests, and what changed since the contributor was last here, without touching the working tree.

    41k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

More from fjrevoredo/mini-diarium

All 41 skills in this repo
  • Manual Planning

    fjrevoredo/mini-diarium

    Create, update, review, and execute manual Markdown implementation plans when harness planning mode is not being used.

    308 GitHub stars~3.7k tokensUpdated 2 days ago
    Auto-check passed
  • M10 Performance

    fjrevoredo/mini-diarium

    CRITICAL: Use for performance optimization. An agent skill from fjrevoredo/mini-diarium.

    308 GitHub starsUsed in 2 repos~1k tokens
    Auto-check passed
  • Solidjs

    fjrevoredo/mini-diarium

    SolidJS framework development skill for building reactive web applications with fine-grained reactivity.

    308 GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed
  • Rust Symbol Analyzer

    fjrevoredo/mini-diarium

    Analyze Rust project structure using LSP symbols. An agent skill from fjrevoredo/mini-diarium.

    308 GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed
  • Tauri V2

    fjrevoredo/mini-diarium

    Tauri v2 cross-platform app development with Rust backend. An agent skill from fjrevoredo/mini-diarium.

    308 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed
  • Exploration Mode

    fjrevoredo/mini-diarium

    Enter exploration mode: a thinking partner for researching and thinking through ideas and problems before implementation.

    308 GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Rust Call Graph

What does Rust Call Graph do?

Visualize Rust function call graphs using LSP. An agent skill from fjrevoredo/mini-diarium. Rust Call Graph is an agent skill from fjrevoredo/mini-diarium. Visualize Rust function call graphs using LSP.

When should I use Rust Call Graph?

Rust Call Graph fits situations like: tasks that involve Codebase onboarding; tasks that involve Incident response.

How do I install Rust Call Graph in Claude Code?

Run `npx skills add fjrevoredo/mini-diarium --skill rust-call-graph -a claude-code`. Or copy the skill folder (.agents/skills/rust-call-graph in fjrevoredo/mini-diarium) into .claude/skills/rust-call-graph in your project. Claude Code loads it when a task matches its description.

How do I install Rust Call Graph in Codex?

Run `npx skills add fjrevoredo/mini-diarium --skill rust-call-graph -a codex`. Or copy the skill folder (.agents/skills/rust-call-graph in fjrevoredo/mini-diarium) into .agents/skills/rust-call-graph in your project. Codex loads it when a task matches its description.

Can I use Rust Call Graph in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fjrevoredo/mini-diarium --skill rust-call-graph -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-call-graph, .gemini/skills/rust-call-graph, .github/skills/rust-call-graph and .opencode/skills/rust-call-graph in your project.

What does Rust Call Graph need to run?

SKILL.md names no scripts, command-line tools or credentials: Rust Call Graph is instructions for the agent only. Its frontmatter pre-approves these tools: LSP, Read, Glob.

Does Rust Call Graph access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rust Call Graph safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rust Call Graph use?

Rust Call Graph is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rust Call Graph use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rust Call Graph?

Skills that share tags, products or a category with Rust Call Graph: Deepwiki Rs (sopaco/deepwiki-rs, 3.1k stars), tilth Code Reading CLI (jahala/tilth, 352 stars), Project Structure (Eynzof/Hermes-CN-Desktop, 1.7k stars) and Codex Proxy RS Development Guide (zyycn/codex-proxy-rs, 738 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rust Call Graph?

fjrevoredo (a GitHub user) maintains it in fjrevoredo/mini-diarium, which has 308 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 4, 2026.

Source: fjrevoredo/mini-diarium on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.