Agent skill · data analytics · github
codebase-memory-mcp
Use when exploring unfamiliar code, mapping architecture, finding symbols or relationships, tracing callers, callees, data flow or dependencies, assessing impact, auditing dead or complex code, or handling explicit Codebase Memory requests. Otherwise skip tasks confined to a supplied known file, tiny one-file check, exact literal, configuration value, error string, or non-code text.
Why this skill is useful
Provides specific commands and workflows for utilizing the Codebase Memory MCP server that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Codebase Memory MCP Use the configured Codebase Memory graph as a discovery accelerator, not as the sole source of truth. Confirm graph-derived conclusions with source snippets or local files before editing code or making strong claims. Evidence Levels Scout — Provisional positive orientation only. Do not make absence, exhaustive, dead-code, or complete-impact claims. Verify — Default for task-directed work. Check freshness where material, exact source snippets, relevant traces, path coverage, and every result page needed by the claim. Auditor — Use for negative, exhaustive, security, dead-code, architecture-boundary, and complete-impact work. Require the current index generation, a bounded scope, complete result streams, coverage inspection, and source checks for gaps. Match the evidence level to the claim. If Auditor evidence cannot be completed, state the bounded limitation instead of making an absolute claim. Workflow 1. Discover the Codebase Memory tools exposed by the current MCP client; clients may prefix or rename tool namespaces. 2. Call listprojects first. Select only the entry whose canonical rootpath matches the live checkout, and retain both its exact project name and root for later calls. If no entry matches, continue with rooted local exploration or ask before indexing when graph access is important; never substitute a similarly named project. 3. Before branch-sensitive or edit-sensitive conclusions, use indexstatus and verify the actual version-control state. Use detectchanges only when its Git base and head are valid for the checkout. If it unexpectedly reports zero changes, or the checkout uses another VCS, inspect that VCS's status or diff before claiming no impact. 4. Use getarchitecture once for unfamiliar structure. Request clusters to discover de-facto module seams. Treat cycles as an opt-in whole-call-graph scan: path does not scope cycle detection, so verify relevant cycles before making module-local claims. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/codebase-memory-mcp