codebase-memory-tracing

Name: codebase-memory-tracing
Availability: InStock
Author: gganbukim

Trace call chains and dependencies for functions across a codebase.

Updated May 4, 2026

Search Tags:#debugging #refactoring #code navigation #call graph #change analysis #codebase tracing #dependency impact

Ready to run

npx skills add https://github.com/gganbukim1/myskills --skill codebase-memory-tracing-gganbukim1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codebase-memory-tracing
Source: https://github.com/gganbukim1/myskills/tree/main/codebase-memory-tracing
Command: npx skills add https://github.com/gganbukim1/myskills --skill codebase-memory-tracing-gganbukim1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing who calls a function, what a function calls, and what the downstream impact is when making changes.

Core Features & Use Cases

Call path tracing: Identify callers and callees by function name using codebase-memory-mcp tracing tools.
Dependency and impact analysis: Assess risk_labels by combining change detection with call-path context.
Use case: You’re preparing a refactor and need to understand every place a function is invoked, plus what other modules will be affected.

Quick Start

Ask the skill to trace dependencies for a specific function in both directions by providing the function name and requesting a full call context.

Frequently Asked Questions about codebase-memory-tracing

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

FAQPage Schema

How do I trace a function call chain across my codebase to find callers and callees?▼

Trace a function call chain across your codebase by using codebase-memory-mcp tracing tools to identify all callers and callees in both directions by function name.

What is the best way to analyze dependency impact before refactoring a function?▼

Analyze dependency impact before refactoring by combining call-path context with change detection to assess risk labels for downstream modules affected by the modification.

How does call graph tracing work for debugging code changes?▼

Call graph tracing for debugging works by executing trace_call_path with direction set to both, mapping the exact invocation flow to isolate root causes and affected dependencies.

Can I identify every place a function is invoked to plan a safe codebase refactor?▼

You can identify every invocation point for a safe codebase refactor by resolving exact function names with search_graph and tracing dependencies in both directions.

Do I need to resolve exact function names before tracing dependencies?▼

Yes, you need to resolve exact function names using codebase-memory-mcp search_graph before running trace_call_path to ensure precise dependency and caller identification.