CATEGORY_NAME

Traverse symbol graphs to reveal callers, callees, and definers across a codebase.

1|Updated May 29, 2026
One-click install
npx skills add https://github.com/aimasteracc/mycelium --skill category-name
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CATEGORY_NAME
Source: https://github.com/aimasteracc/mycelium/tree/main/skills/_template
Command: npx skills add https://github.com/aimasteracc/mycelium --skill category-name

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps and traverses the symbol graph in a codebase to reveal relationships like callers, callees, definers, and impact, enabling faster navigation and impact analysis.

Core Features & Use Cases

  • Symbol-graph navigation: identify relationships between functions, methods, and symbols across modules.
  • Impact analysis: determine what code paths are affected by a change.
  • Quick navigation workflows: jump from a symbol to its callers, callees, or definers to understand dependencies.

Quick Start

Query the symbol graph to locate a symbol's callers, callees, and definers across the repository.

Frequently Asked Questions about CATEGORY_NAME

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

FAQPage Schema
How do I perform impact analysis to see what code paths are affected by a change?

To perform impact analysis, query the symbol graph to locate a symbol's callers, callees, and definers across the repository. This reveals affected code paths and dependencies across modules.

What is a symbol graph and how does it help with code navigation?

A symbol graph represents relationships between functions, methods, and symbols across modules. It enables fast code navigation by allowing you to query callers, callees, and definers to understand dependencies.

How do I find all callers and callees for a specific function across modules?

You find callers and callees by querying the symbol graph to traverse relationships for the target function. This identifies where the function is invoked and what downstream dependencies it calls across the repository.

Can I use symbol graph navigation for large codebases with many modules?

Yes, symbol graph navigation supports large codebases by providing fast traversal and accurate filtering across modules. It is designed to map calls and impacts efficiently across extensive repositories.

What's the best way to map dependencies before modifying shared methods?

The best way to map dependencies is querying the symbol graph for definers and callers. This reveals the full impact of changes across modules, preventing unintended breakage before modifying shared methods.