call-graph

Analyze symbol call relationships and generate call trees across codebases.

1|Updated May 29, 2026

Search Tags:#static-analysis #code-analysis #call-graph #callers #dependency-graph #callees #symbol-calls

Ready to run

npx skills add https://github.com/aimasteracc/mycelium --skill call-graph

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: call-graph
Source: https://github.com/aimasteracc/mycelium/tree/main/skills/call-graph
Command: npx skills add https://github.com/aimasteracc/mycelium --skill call-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill bundles capabilities to identify and analyze call relationships between symbols in a codebase, revealing callers, callees, entry points, and code-health signals like dead or isolated symbols.

Core Features & Use Cases

Direct and transitive queries: find current call relationships and build recursive trees for deeper impact analysis.
Entry-point discovery & health checks: detect root functions and unreachable symbols to guide refactors.
Refactor planning & risk assessment: understand blast-radius and dependencies before renaming or removing symbols.

Quick Start

Ask for the callers or callee-tree of a symbol to quickly understand its reachability.

Frequently Asked Questions about call-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find all callers of a function in a large multi-language codebase?▼

To find callers of a function, use the get_callers tool to identify direct call relationships between symbols in a large codebase. This reveals who calls whom and helps map dependencies for refactor planning and risk assessment.

What is a call graph and when do I need it for code analysis?▼

A call graph maps the calling relationships between symbols so you can see callers, callees, and entry points. You need it for static code analysis, refactor planning, code health diagnostics, and dependency impact assessment.

How do I check the blast-radius before renaming or removing a symbol?▼

Check the blast-radius of a symbol by generating a recursive caller-tree or callee-tree. This builds transitive dependency trees to understand the full impact and reachability before modifying or removing code.

Can I detect dead symbols and entry points in a static codebase analysis?▼

Yes, you can detect dead symbols and entry points using get_dead_symbols and get_entry_points. These health checks identify root functions and unreachable code to guide refactoring and dependency cleanup.

Does static call graph analysis work for large, multi-language codebases?▼

Static call graph analysis supports large, multi-language codebases by identifying symbol paths and call relationships across the project. You can use depth controls to manage the complexity of recursive transitive queries.