Agent skill

Codebase Memory Tracing

This skill should be used when the user asks "who calls this function", "what does X call", "trace the call chain", "find callers of", "show dependencies", "what depends on", "trace call path"…

GPL-3.0Auto-check passed

Install Codebase Memory Tracing

skills CLI

$ npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install DmNote-App/DmNote codebase-memory-tracing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/DmNote-App/DmNote.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/codebase-memory-tracing .claude/skills/codebase-memory-tracing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "codebase-memory-tracing" agent skill from https://github.com/DmNote-App/DmNote/tree/main/.codex/skills/codebase-memory-tracing into .claude/skills/codebase-memory-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codebase-memory-tracing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/DmNote-App/DmNote/tree/main/.codex/skills/codebase-memory-tracing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install DmNote-App/DmNote codebase-memory-tracing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DmNote-App/DmNote.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/codebase-memory-tracing .agents/skills/codebase-memory-tracing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "codebase-memory-tracing" agent skill from https://github.com/DmNote-App/DmNote/tree/main/.codex/skills/codebase-memory-tracing into .agents/skills/codebase-memory-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codebase-memory-tracing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install DmNote-App/DmNote codebase-memory-tracing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DmNote-App/DmNote.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/codebase-memory-tracing .cursor/skills/codebase-memory-tracing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "codebase-memory-tracing" agent skill from https://github.com/DmNote-App/DmNote/tree/main/.codex/skills/codebase-memory-tracing into .cursor/skills/codebase-memory-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codebase-memory-tracing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/DmNote-App/DmNote.git --path .codex/skills/codebase-memory-tracing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install DmNote-App/DmNote codebase-memory-tracing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DmNote-App/DmNote.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/codebase-memory-tracing .gemini/skills/codebase-memory-tracing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "codebase-memory-tracing" agent skill from https://github.com/DmNote-App/DmNote/tree/main/.codex/skills/codebase-memory-tracing into .gemini/skills/codebase-memory-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codebase-memory-tracing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install DmNote-App/DmNote codebase-memory-tracing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/DmNote-App/DmNote.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/codebase-memory-tracing .github/skills/codebase-memory-tracing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "codebase-memory-tracing" agent skill from https://github.com/DmNote-App/DmNote/tree/main/.codex/skills/codebase-memory-tracing into .github/skills/codebase-memory-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codebase-memory-tracing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install DmNote-App/DmNote codebase-memory-tracing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/DmNote-App/DmNote.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/codebase-memory-tracing .opencode/skills/codebase-memory-tracing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "codebase-memory-tracing" agent skill from https://github.com/DmNote-App/DmNote/tree/main/.codex/skills/codebase-memory-tracing into .opencode/skills/codebase-memory-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "codebase-memory-tracing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: codebase-memory-tracing
GitHub stars: 2.4k
Token cost: ~1.1k tokens
SKILL.md length: 334 words
Files: 1
Skills in repo: 7
Repo updated: Sep 30, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

This skill should be used when the user asks "who calls this function", "what does X call", "trace the call chain", "find callers of", "show dependencies", "what depends on", "trace call path"…

Works in 5 steps: Discover the exact function name → Trace callers (who calls this function?) → Trace callees (what does this function… → …
Asks who calls this function
SKILL.md covers Workflow, Cross-Service HTTP Calls, Async Dispatch (Cloud Tasks,… and Interface Implementations, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Codebase Memory Tracing is an agent skill from DmNote-App/DmNote. This skill should be used when the user asks "who calls this function", "what does X call", "trace the call chain", "find callers of", "show dependencies", "what depends on", "trace call path", "find all references to", "impact analysis", or needs to understand function call relationships and dependency chains.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Make it yours. A customizable key viewer for DJMAX RESPECT V and any game. The licence is GPL-3.0.

When your agent uses it

Asks who calls this function
What does X call
Trace the call chain
Find callers of

Example prompts

“who calls this function”
“what does X call”
“trace the call chain”
“/codebase-memory-tracing”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Discover the exact function name
Trace callers (who calls this function?)
Trace callees (what does this function call?)
Full context (both callers and callees)
Read suspicious code

What it can do on your machine

Read from SKILL.md and the folder at commit baac1e8. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Codebase Memory Tracing loads about 1.1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 334 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~84
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from DmNote-App/DmNote at commit baac1e8, republished under its GPL-3.0 licence (© DmNote-App). 334 words, ~1,060 tokens.

Download SKILL.mdSave it as .claude/skills/codebase-memory-tracing/SKILL.md (or your agent's skills folder).

name: codebase-memory-tracing
description: This skill should be used when the user asks "who calls this function", "what does X call", "trace the call chain", "find callers of", "show dependencies", "what depends on", "trace call path", "find all references to", "impact analysis", or needs to understand function call relationships and dependency chains.

Call Chain Tracing via Knowledge Graph

Use graph tools to trace function call relationships. One trace_call_path call replaces dozens of grep searches across files.

Workflow

Step 1: Discover the exact function name

trace_call_path requires an exact name match. If you don't know the exact name, discover it first with regex:

search_graph(name_pattern=".*Order.*", label="Function")

Use full regex for precise discovery — no full-text search needed:

(?i)order — case-insensitive
^(Get|Set|Delete)Order — CRUD variants
.*Order.*Handler$ — handlers only
qn_pattern=".*services\\.order\\..*" — scope to order service directory

This returns matching functions with their qualified names and file locations.

Step 2: Trace callers (who calls this function?)

trace_call_path(function_name="ProcessOrder", direction="inbound", depth=3)

Returns a hop-by-hop list of all functions that call ProcessOrder, up to 3 levels deep.

Step 3: Trace callees (what does this function call?)

trace_call_path(function_name="ProcessOrder", direction="outbound", depth=3)

Step 4: Full context (both callers and callees)

trace_call_path(function_name="ProcessOrder", direction="both", depth=3)

Always use direction="both" for complete context. Cross-service HTTP_CALLS edges from other services appear as inbound edges — direction="outbound" alone misses them.

Step 5: Read suspicious code

After finding interesting callers/callees, read their source:

get_code_snippet(qualified_name="project.path.module.FunctionName")

Cross-Service HTTP Calls

To see all HTTP links between services with URLs and confidence scores:

query_graph(query="MATCH (a)-[r:HTTP_CALLS]->(b) RETURN a.name, b.name, r.url_path, r.confidence ORDER BY r.confidence DESC LIMIT 20")

Filter by URL path:

query_graph(query="MATCH (a)-[r:HTTP_CALLS]->(b) WHERE r.url_path CONTAINS '/orders' RETURN a.name, b.name, r.url_path")

Async Dispatch (Cloud Tasks, Pub/Sub, etc.)

Find dispatch functions by name pattern, then trace:

search_graph(name_pattern=".*CreateTask.*|.*send_to_pubsub.*")
trace_call_path(function_name="CreateMultidataTask", direction="both")

Interface Implementations

Find which structs implement an interface method:

query_graph(query="MATCH (s)-[r:OVERRIDE]->(i) WHERE i.name = 'Read' RETURN s.name, i.name LIMIT 20")

Read References (callbacks, variable assignments)

query_graph(query="MATCH (a)-[r:USAGE]->(b) WHERE b.name = 'ProcessOrder' RETURN a.name, a.file_path LIMIT 20")

Risk-Classified Impact Analysis

Add risk_labels=true to get risk classification on each node:

trace_call_path(function_name="ProcessOrder", direction="inbound", depth=3, risk_labels=true)

Returns nodes with risk (CRITICAL/HIGH/MEDIUM/LOW) based on hop depth, plus an impact_summary with counts. Risk mapping: hop 1=CRITICAL, 2=HIGH, 3=MEDIUM, 4+=LOW.

Detect Changes (Git Diff Impact)

Map uncommitted changes to affected symbols and their blast radius:

detect_changes()
detect_changes(scope="staged")
detect_changes(scope="branch", base_branch="main")

Returns changed files, changed symbols, and impacted callers with risk classification. Scopes: unstaged, staged, all (default), branch.

Key Tips

Start with depth=1 for quick answers, increase only if needed (max 5).
Edge types in trace results: CALLS (direct), HTTP_CALLS (cross-service), ASYNC_CALLS (async dispatch), USAGE (read reference), OVERRIDE (interface implementation).
search_graph(relationship="HTTP_CALLS") filters nodes by degree — it does NOT return edges. Use query_graph with Cypher to see actual edges with properties.
Results are capped at 200 nodes per trace.
detect_changes requires git in PATH.

Files

Just SKILL.md in .codex/skills/codebase-memory-tracing of DmNote-App/DmNote.

Open the folder on GitHubat commit baac1e8

Compare with similar skills

Codebase Memory Tracing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Codebase Memory Tracing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Codebase Memory Tracing this skillDmNote-App/DmNote	2.4k	—	~1.1k	Automated safety check: Pass	GPL-3.0	7 days ago
Observe Traceruvnet/ruflo	74k	—	~522	Automated safety check: Notes	MIT	yesterday
Tracezereight/gitlab-mcp	2k	1 repos	~412	Automated safety check: Pass	MIT	2 days ago
Distributed Tracingwshobson/agents	40k	11 repos	~527	Automated safety check: Pass	MIT	3 days ago
Arize Tracegithub/awesome-copilot	40k	1 repos	~5.9k	Automated safety check: Notes	MIT	yesterday
Evidence-Driven TraceYeachan-Heo/oh-my-claudecode	40k	—	~2.6k	Automated safety check: Pass	MIT	yesterday

Similar skills

Observe Trace
ruvnet/ruflo
Trace agent execution by collecting spans and building a trace tree for a task
74k GitHub stars~522 tokensUpdated yesterday
Auto-check: notes
Trace
zereight/gitlab-mcp
Evidence-driven tracing with competing hypotheses in parallel.
2k GitHub starsUsed in 1 repo~412 tokens
DevelopmentAuto-check passed
Distributed Tracing
wshobson/agents
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.
40k GitHub starsUsed in 11 repos~527 tokens
DevOps & CloudAuto-check passed
Arize Trace
github/awesome-copilot
Official
Downloads, exports, and inspects existing Arize traces and spans to understand what an LLM app is doing or debug runtime issues.
40k GitHub starsUsed in 1 repo~5.9k tokens
DevelopmentAuto-check: notes
Evidence-Driven Trace
Yeachan-Heo/oh-my-claudecode
Explains why something happened by generating competing hypotheses, gathering evidence in parallel, ranking explanations and proposing the next discriminating probe.
40k GitHub stars~2.6k tokensUpdated yesterday
DevelopmentAuto-check passed
KubeSphere WizTelemetry Tracing
kubesphere/kubesphere
Installs and configures WizTelemetry Tracing for KubeSphere, an OpenTelemetry-based tracing extension, and covers its components, query API and auto-instrumentation.
17k GitHub stars~4.6k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed

More from DmNote-App/DmNote

Codebase Memory Exploring
DmNote-App/DmNote
This skill should be used when the user asks to "explore the codebase", "understand the architecture", "what functions exist", "show me the structure", "how is the code organized", "find functions…
2.4k GitHub stars~576 tokensUpdated 7 days ago
Auto-check passed
Codebase Memory Quality
DmNote-App/DmNote
This skill should be used when the user asks about "dead code", "find dead code", "detect dead code", "show dead code", "dead code analysis", "unused functions", "find unused functions"…
2.4k GitHub stars~683 tokensUpdated 7 days ago
Auto-check passed
Codebase Memory Reference
DmNote-App/DmNote
This skill should be used when the user asks about "codebase-memory-mcp tools", "graph query syntax", "Cypher query examples", "edge types", "how to use searchgraph", "querygraph examples", or needs…
2.4k GitHub stars~1.7k tokensUpdated 7 days ago
Auto-check passed
Agent Debug
DmNote-App/DmNote
원인이 불명확한 버그를 독립 서브에이전트와 병렬로 추적한다. An agent skill from DmNote-App/DmNote.
2.4k GitHub stars~249 tokensUpdated 7 days ago
Auto-check passed
Agent Plan
DmNote-App/DmNote
구현 전 독립 서브에이전트에게 계획을 검증받는다. An agent skill from DmNote-App/DmNote.
2.4k GitHub stars~234 tokensUpdated 7 days ago
Auto-check passed
Agent Review
DmNote-App/DmNote
독립 서브에이전트의 적대적 코드 리뷰. An agent skill from DmNote-App/DmNote.
2.4k GitHub stars~307 tokensUpdated 7 days ago
Auto-check passed

Questions about Codebase Memory Tracing

What does Codebase Memory Tracing do?

This skill should be used when the user asks "who calls this function", "what does X call", "trace the call chain", "find callers of", "show dependencies", "what depends on", "trace call path"…. Codebase Memory Tracing is an agent skill from DmNote-App/DmNote. This skill should be used when the user asks "who calls this function", "what does X call", "trace the call chain", "find callers of", "show dependencies", "what depends on", "trace call path", "find all references to", "impact analysis", or needs to understand function call relationships and dependency chains.

When should I use Codebase Memory Tracing?

Codebase Memory Tracing fits situations like: asks who calls this function; what does X call; trace the call chain; find callers of.

How do I install Codebase Memory Tracing in Claude Code?

Run `npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a claude-code`. Or copy the skill folder (.codex/skills/codebase-memory-tracing in DmNote-App/DmNote) into .claude/skills/codebase-memory-tracing in your project. Claude Code loads it when a task matches its description.

How do I install Codebase Memory Tracing in Codex?

Run `npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a codex`. Or copy the skill folder (.codex/skills/codebase-memory-tracing in DmNote-App/DmNote) into .agents/skills/codebase-memory-tracing in your project. Codex loads it when a task matches its description.

Can I use Codebase Memory Tracing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DmNote-App/DmNote --skill codebase-memory-tracing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/codebase-memory-tracing, .gemini/skills/codebase-memory-tracing, .github/skills/codebase-memory-tracing and .opencode/skills/codebase-memory-tracing in your project.

What does Codebase Memory Tracing need to run?

SKILL.md names no scripts, command-line tools or credentials: Codebase Memory Tracing is instructions for the agent only.

Does Codebase Memory Tracing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Codebase Memory Tracing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Codebase Memory Tracing use?

Codebase Memory Tracing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Codebase Memory Tracing use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Codebase Memory Tracing?

Skills that share tags, products or a category with Codebase Memory Tracing: Observe Trace (ruvnet/ruflo, 74k stars), Trace (zereight/gitlab-mcp, 2k stars), Distributed Tracing (wshobson/agents, 40k stars) and Arize Trace (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Codebase Memory Tracing?

DmNote-App (a GitHub organization) maintains it in DmNote-App/DmNote, which has 2,403 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 30, 2026.

Source: DmNote-App/DmNote on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Codebase Memory Tracing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Call Chain Tracing via Knowledge Graph

Workflow

Step 1: Discover the exact function name

Step 2: Trace callers (who calls this function?)

Step 3: Trace callees (what does this function call?)

Step 4: Full context (both callers and callees)

Step 5: Read suspicious code

Cross-Service HTTP Calls

Async Dispatch (Cloud Tasks, Pub/Sub, etc.)

Interface Implementations

Read References (callbacks, variable assignments)

Risk-Classified Impact Analysis

Detect Changes (Git Diff Impact)

Key Tips

Files

Compare with similar skills

Similar skills

More from DmNote-App/DmNote

Questions about Codebase Memory Tracing