architecture-context

Identify entry points and call graph context for natural-language code tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand how a codebase works by locating entry points, nearby call relationships, and relevant source locations for a given task or question.

Core Features & Use Cases

  • One-shot orientation: surface entry points, call-graph neighborhood, and source spans in a single query.
  • CLI and MCP surfaces: available via mycelium_context and the mycelium context CLI for flexible workflows.
  • Use case: ideal for onboarding new code areas, debugging architectures, and performing top-down codebase tracing.

Quick Start

Describe entry points, call graph neighborhood, and source spans for a given module.

Frequently Asked Questions about architecture-context

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

FAQPage Schema
How do I trace code architecture and entry points for an unfamiliar codebase?

You can trace code architecture by providing a natural-language task description. The Skill then surfaces relevant entry points, nearby call graph relationships, and source spans to help you quickly understand how the codebase works.

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

Call graph context exposes the nearby call relationships and source locations surrounding entry points. You need it when onboarding to new code areas, debugging architectures, or performing top-down codebase tracing to plan focused queries.

Can I use this architecture context tracing tool with both CLI and MCP surfaces?

Yes, architecture context tracing is available via both the mycelium context CLI and the mycelium_context MCP surface. Both interfaces return entry_points, nodes, and edges to support flexible workflows.

What's the best way to get one-shot context for a specific module's architecture?

The best way to get one-shot context is to describe the module or task in natural language. The Skill then returns entry points, the call graph neighborhood, and source spans in a single query for rapid orientation.

Does this code analysis tool require any dependencies to trace call graphs?

No, this code analysis tool requires no dependencies to trace call graphs. It identifies and exposes entry points and call graph context directly from a natural-language task query.