code-graph

Query indexed code graphs to trace symbols, dependencies, and callers.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill code-graph-lciacci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-graph
Source: https://github.com/lciacci/tessera/tree/main/skills/code-graph
Command: npx skills add https://github.com/lciacci/tessera --skill code-graph-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inefficient, error-prone codebase navigation by replacing broad file reads and manual searches with targeted graph-based analysis of symbols, dependencies, callers, and change impact.

Core Features & Use Cases

  • Symbol Discovery: Quickly locate functions, classes, modules, and code patterns across a repository.
  • Dependency and Impact Analysis: Trace call paths, understand architecture, and assess blast radius before changing shared code.
  • Graph-First Workflow: Combine architecture inspection, targeted snippets, freshness checks, and change detection to plan and verify implementation work.
  • Use Case: Before refactoring a shared authentication function, identify its definition, inspect its callers, trace related dependencies, and evaluate the likely blast radius before editing the implementation.

Quick Start

Ask the code-graph skill to map the architecture and trace all callers of the symbol you plan to change.

Frequently Asked Questions about code-graph

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

FAQPage Schema
How do I assess the blast radius before refactoring shared code?

Dependency analysis traces call paths and symbol callers to evaluate blast radius before refactoring shared code. This graph-based approach replaces brute-force file searching with targeted impact analysis to safely navigate and modify complex architectures.

What is the best way to discover code architecture without reading entire files?

Graph-based symbol lookup enables architecture discovery by mapping functions, classes, and modules across a repository. This method replaces broad file reads with targeted code navigation, identifying dependencies and structural patterns efficiently.

How do I trace callers and dependencies of a specific function in a large codebase?

Call tracing uses graph queries to locate function definitions and map all related callers and dependencies. This code navigation method relies on an indexed repository to provide up-to-date structural data for accurate dependency analysis.

Do I need an indexed repository to perform graph-based code navigation?

Yes, graph-based code navigation requires an indexed repository and the codebase-memory-mcp MCP server. This environment provides the structured graph queries necessary for accurate symbol lookup, dependency analysis, and call tracing.

Can I use graph queries to plan implementation work and verify code changes?

Yes, a graph-first workflow combines architecture inspection, targeted snippets, and freshness checks to plan and verify implementation work. This ensures code changes are validated against current dependency structures and call paths before editing.