Build Graph
- 1k installs
- 28.5k repo stars
- Updated August 2, 2026
- tirth8205/code-review-graph
build-graph is a code-review-graph agent skill that builds or incrementally updates a persistent repository knowledge graph via MCP tools for developers who need context-aware intelligent code reviews.
About
build-graph from tirth8205/code-review-graph initializes or updates the persistent code knowledge graph backing intelligent code reviews. The workflow checks graph status with list_graph_stats_tool, performs a full build when last_updated is null via build_or_update_graph_tool(full_rebuild=True), or runs incremental updates on existing graphs. Hooks can keep the graph current automatically between reviews. Developers run build-graph first on a new repository or pass a full argument to force rebuild when review context is stale or incomplete.
- Initializes or incrementally updates a persistent SQLite code-review knowledge graph
- Automatically detects when a full rebuild versus incremental update is required
- Parses Python, TypeScript, JavaScript, Vue, Go, Rust, Java and 9 other languages
- Respects .code-review-graphignore and skips binary/generated files
- Verifies results with node/edge counts, languages detected, and error reporting
Build Graph by the numbers
- 1,043 all-time installs (skills.sh)
- +32 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #119 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/tirth8205/code-review-graph --skill build-graphAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1k |
|---|---|
| repo stars | ★ 28.5k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | tirth8205/code-review-graph ↗ |
How do you build a code review knowledge graph?
Create and maintain a persistent knowledge graph that powers intelligent, context-aware code reviews across their repository.
Who is it for?
Developers using code-review-graph who need an initialized or updated knowledge graph before context-aware reviews.
Skip if: Developers seeking one-off diff reviews without persistent graph infrastructure or MCP tool access.
When should I use this skill?
A repository has no graph yet, graph stats show null last_updated, or an incremental graph refresh is needed before review.
What you get
Persistent repository knowledge graph with stats, last_updated timestamp, and incremental or full rebuild state.
- persistent code knowledge graph
- graph stats with last_updated
- incremental or full graph index
Files
Build Graph
Build or incrementally update the persistent code knowledge graph for this repository.
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-graphignoreare skipped - Supported languages: Python, TypeScript/JavaScript, Vue, Go, Rust, Java, Scala, C#, Ruby, Kotlin, Swift, PHP, Solidity, C/C++
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kHow it compares
Run build-graph before review skills when persistent repo context is required; skip it for lightweight single-file diff reviews.
FAQ
When should build-graph run a full rebuild?
build-graph calls list_graph_stats_tool first. When last_updated is null—the graph was never built—it runs build_or_update_graph_tool with full_rebuild=True. Existing graphs receive incremental updates instead.
What MCP tools does build-graph use?
build-graph uses list_graph_stats_tool to check graph status and build_or_update_graph_tool to create or update the persistent code knowledge graph. Hooks can trigger automatic incremental updates between manual runs.
Is Build Graph safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.