40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
---
|
|
description: Build or rebuild the code review knowledge graph for this project.
|
|
agent: build
|
|
---
|
|
|
|
# Build Graph
|
|
|
|
Build or incrementally update the persistent code knowledge graph for this repository.
|
|
|
|
$ARGUMENTS
|
|
|
|
## Steps
|
|
|
|
1. **Check graph status** by calling the `list_graph_stats_tool` MCP tool.
|
|
- If the graph has never been built (last_updated is null), proceed with a full build.
|
|
- If the graph exists, proceed with an incremental update.
|
|
|
|
2. **Build the graph** by calling the `build_or_update_graph_tool` MCP tool:
|
|
- For first-time setup: `build_or_update_graph_tool(full_rebuild=True)`
|
|
- For updates: `build_or_update_graph_tool()` (incremental by default)
|
|
|
|
3. **Verify** by calling `list_graph_stats_tool` again and report the results:
|
|
- Number of files parsed
|
|
- Number of nodes and edges created
|
|
- Languages detected
|
|
- Any errors encountered
|
|
|
|
## When to Use
|
|
|
|
- First time setting up the graph for a repository
|
|
- After major refactoring or branch switches
|
|
- If the graph seems stale or out of sync
|
|
- The graph auto-updates via hooks on edit/commit, so manual builds are rarely needed
|
|
|
|
## Notes
|
|
|
|
- The graph is stored as a SQLite database (`.code-review-graph/graph.db`) in the repo root
|
|
- Binary files, generated files, and patterns in `.code-review-graphignore` are skipped
|
|
- If the graph tools are unavailable, fall back to `code-review-graph build` / `code-review-graph status` via the shell
|