How do I install the Codebase Memory skill?

Run npx skillmds@latest add gdm257/codebase-memory in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Codebase Memory skill do?

Codebase Memory — Knowledge Graph Tools It is listed under Coding & Dev Tools on SkillMD.

Is Codebase Memory safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codebase Memory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codebase Memory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codebase Memory?

gdm257 (@gdm257) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codebase Memory by gdm257 — Agent Skill

Name: Codebase Memory
Author: gdm257

File contents

Codebase Memory — Knowledge Graph Tools

Graph tools return precise structural results in ~500 tokens vs ~80K for grep.

Quick Decision Matrix

Question	Tool call
Who calls X?	`trace_path(direction="inbound")`
What does X call?	`trace_path(direction="outbound")`
Full call context	`trace_path(direction="both")`
Find by name pattern	`search_graph(name_pattern="...")`
Dead code	`search_graph(max_degree=0, exclude_entry_points=true)`
Cross-service edges	`query_graph` with Cypher
Impact of local changes	`detect_changes()`
Risk-classified trace	`trace_path(risk_labels=true)`
Text search	`search_code` or Grep

Exploration Workflow

list_projects — check if project is indexed
get_graph_schema — understand node/edge types
search_graph(label="Function", name_pattern=".*Pattern.*") — find code
get_code_snippet(qualified_name="project.path.FuncName") — read source

Tracing Workflow

search_graph(name_pattern=".*FuncName.*") — discover exact name
trace_path(function_name="FuncName", direction="both", depth=3) — trace
detect_changes() — map git diff to affected symbols

Quality Analysis

Dead code: search_graph(max_degree=0, exclude_entry_points=true)
High fan-out: search_graph(min_degree=10, relationship="CALLS", direction="outbound")
High fan-in: search_graph(min_degree=10, relationship="CALLS", direction="inbound")

14 MCP Tools

index_repository, index_status, list_projects, delete_project, search_graph, search_code, trace_path, detect_changes, query_graph, get_graph_schema, get_code_snippet, get_architecture, manage_adr, ingest_traces

Edge Types

CALLS, HTTP_CALLS, ASYNC_CALLS, IMPORTS, DEFINES, DEFINES_METHOD, HANDLES, IMPLEMENTS, OVERRIDE, USAGE, FILE_CHANGES_WITH, CONTAINS_FILE, CONTAINS_FOLDER, CONTAINS_PACKAGE

Cypher Examples (for query_graph)

MATCH (a)-[r:HTTP_CALLS]->(b) RETURN a.name, b.name, r.url_path, r.confidence LIMIT 20
MATCH (f:Function) WHERE f.name =~ '.*Handler.*' RETURN f.name, f.file_path
MATCH (a)-[r:CALLS]->(b) WHERE a.name = 'main' RETURN b.name

Gotchas

search_graph(relationship="HTTP_CALLS") filters nodes by degree — use query_graph with Cypher to see actual edges.
query_graph has a 200-row cap — use search_graph with degree filters for counting.
trace_path needs exact names — use search_graph(name_pattern=...) first.
direction="outbound" misses cross-service callers — use direction="both".
Results default to 10 per page — check has_more and use offset.

---name: codebase-memorydescription: Codebase Memory — Knowledge Graph Tools---# Codebase Memory — Knowledge Graph ToolsGraph tools return precise structural results in ~500 tokens vs ~80K for grep.## Quick Decision Matrix| Question | Tool call ||----------|----------|| Who calls X? | `trace_path(direction="inbound")` || What does X call? | `trace_path(direction="outbound")` || Full call context | `trace_path(direction="both")` || Find by name pattern | `search_graph(name_pattern="...")` || Dead code | `search_graph(max_degree=0, exclude_entry_points=true)` || Cross-service edges | `query_graph` with Cypher || Impact of local changes | `detect_changes()` || Risk-classified trace | `trace_path(risk_labels=true)` || Text search | `search_code` or Grep |## Exploration Workflow1. `list_projects` — check if project is indexed2. `get_graph_schema` — understand node/edge types3. `search_graph(label="Function", name_pattern=".*Pattern.*")` — find code4. `get_code_snippet(qualified_name="project.path.FuncName")` — read source## Tracing Workflow1. `search_graph(name_pattern=".*FuncName.*")` — discover exact name2. `trace_path(function_name="FuncName", direction="both", depth=3)` — trace3. `detect_changes()` — map git diff to affected symbols## Quality Analysis- Dead code: `search_graph(max_degree=0, exclude_entry_points=true)`- High fan-out: `search_graph(min_degree=10, relationship="CALLS", direction="outbound")`- High fan-in: `search_graph(min_degree=10, relationship="CALLS", direction="inbound")`## 14 MCP Tools`index_repository`, `index_status`, `list_projects`, `delete_project`,`search_graph`, `search_code`, `trace_path`, `detect_changes`,`query_graph`, `get_graph_schema`, `get_code_snippet`, `get_architecture`,`manage_adr`, `ingest_traces`## Edge TypesCALLS, HTTP_CALLS, ASYNC_CALLS, IMPORTS, DEFINES, DEFINES_METHOD,HANDLES, IMPLEMENTS, OVERRIDE, USAGE, FILE_CHANGES_WITH,CONTAINS_FILE, CONTAINS_FOLDER, CONTAINS_PACKAGE## Cypher Examples (for query_graph)```MATCH (a)-[r:HTTP_CALLS]->(b) RETURN a.name, b.name, r.url_path, r.confidence LIMIT 20MATCH (f:Function) WHERE f.name =~ '.*Handler.*' RETURN f.name, f.file_pathMATCH (a)-[r:CALLS]->(b) WHERE a.name = 'main' RETURN b.name```## Gotchas1. `search_graph(relationship="HTTP_CALLS")` filters nodes by degree — use `query_graph` with Cypher to see actual edges.2. `query_graph` has a 200-row cap — use `search_graph` with degree filters for counting.3. `trace_path` needs exact names — use `search_graph(name_pattern=...)` first.4. `direction="outbound"` misses cross-service callers — use `direction="both"`.5. Results default to 10 per page — check `has_more` and use `offset`.

Frequently asked questions

Codebase Memory