31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
Start with `docs/development.md` for orientation and use its policy reading guide
|
|
to select the policies applicable to the task. Do not read the entire suite by
|
|
default.
|
|
|
|
Read and follow `docs/policy/agents.md` before recommending, planning, or
|
|
implementing repository changes.
|
|
|
|
<!-- codebase-memory-mcp:start -->
|
|
# 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")`
|
|
<!-- codebase-memory-mcp:end -->
|