codebase-memory-tracing

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

Trace function call relationships across a codebase with graph-based queries.

5|Updated Mar 18, 2026

Search Tags:#codebase #trace #graph #callers #callees #function-calls #call-path

Ready to run

npx skills add https://github.com/sambeau/kanbanzai --skill codebase-memory-tracing-sambeau

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traces function call relationships across a codebase to reveal which functions call others, helping debug and understand complex dependencies.

Core Features & Use Cases

Discover the exact function name with regex-based search to locate targets.
Trace inbound callers to understand who depends on a given function.
Trace outbound callees to map a function's dependencies and impact.
Retrieve full context for a function, including cross-service HTTP calls and inter-module references.
Read relevant code snippets to inspect implementations and call sites.

Quick Start

Trace the call path for a function name to identify its callers and callees up to a chosen depth.

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 function call paths across a codebase?▼

Trace function call paths across a codebase by using graph-based queries to discover targets and traverse inbound callers or outbound callees. You can set depth limits to map dependencies and understand complex relationships.

What is function call tracing used for in software engineering?▼

Function call tracing reveals which functions call others, helping debug and understand complex dependencies. By mapping inbound and outbound relationships, you can assess a function's impact and locate inter-module references.

Can I trace cross-service HTTP calls and inter-module references?▼

Yes, you can retrieve full context for a function, including cross-service HTTP calls and inter-module references. Graph-based queries traverse bidirectional call paths to expose these dependencies.

How do I find the exact function name before tracing its callers and callees?▼

Find the exact function name by running a regex-based search to locate targets within the knowledge graph. This ensures accurate traversal of inbound callers and outbound callees.

What is the best way to limit the depth of a call path trace?▼

Limit the depth of a call path trace by specifying depth limits during your graph query. This constrains the traversal of callers and callees to a chosen level, keeping the dependency map manageable.

Does codebase tracing work with bidirectional call analysis?▼

Yes, codebase tracing supports bidirectional analysis to map both inbound callers and outbound callees. It uses graph queries to traverse dependencies and retrieve relevant code snippets for inspection.