# Codebase Knowledge Graph (codebase-memory-mcp) This project uses codebase-memory-mcp to maintain a knowledge graph of the codebase. ALWAYS prefer MCP graph tools over grep/glob/file-search for code discovery. ## Priority Order 1. `search_graph` — find functions, classes, routes, variables by pattern 2. `trace_path` — trace who calls a function or what it calls 3. `get_code_snippet` — read specific function/class source code 4. `query_graph` — run Cypher queries for complex patterns 5. `get_architecture` — high-level project summary ## When to fall back to grep/glob - Searching for string literals, error messages, config values - Searching non-code files (Dockerfiles, shell scripts, configs) - When MCP tools return insufficient results ## Examples - Find a handler: `search_graph(name_pattern=".*OrderHandler.*")` - Who calls it: `trace_path(function_name="OrderHandler", direction="inbound")` - Read source: `get_code_snippet(qualified_name="pkg/orders.OrderHandler")` ## Agent skills ### Issue tracker Issues and specs live in GitHub Issues; use `gh` CLI. See `docs/agents/issue-tracker.md`. ### Triage labels Use the canonical labels `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, and `wontfix`. See `docs/agents/triage-labels.md`. ### Domain docs This is a single-context repository using root `CONTEXT.md` and `docs/adr/`. See `docs/agents/domain.md`.