build-graph

Build and maintain a persistent code review knowledge graph in SQLite.

8|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/demon24ru/code-review-graph --skill build-graph-demon24ru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-graph
Source: https://github.com/demon24ru/code-review-graph/tree/main/skills/build-graph
Command: npx skills add https://github.com/demon24ru/code-review-graph --skill build-graph-demon24ru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds and maintains a persistent code review knowledge graph for a repository to provide precise context for AI-assisted reviews and incremental code understanding.

Core Features & Use Cases

  • Full or incremental graph builds: initialize or update the knowledge graph as codebases evolve.
  • Graph statistics and verification: query graph status, files parsed, nodes/edges, languages detected.
  • Storage and guardrails: stores the graph in a SQLite database at .code-review-graph/graph.db and honors ignore rules to skip binary content.

Quick Start

Run the build-graph workflow to initialize or update your repository's knowledge graph.

Frequently Asked Questions about build-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a code review knowledge graph for my repository?

You build a code review knowledge graph by running the build-graph workflow, which parses repository files to extract nodes and edges, detects languages, and stores the graph in a SQLite database at .code-review-graph/graph.db.

What is a persistent code review graph and when do I need to update it?

A persistent code review graph is a SQLite database storing parsed code relationships for AI-assisted reviews. You need to initialize it during first-time setup or after major refactors, applying incremental updates as your codebase evolves.

Does the build-graph workflow track repository parsing metrics and detected languages?

Yes, the build-graph workflow records progress metrics including files parsed, nodes and edges created, and detected programming languages, providing graph statistics and verification for your repository context.

Can I use build-graph to skip binary files and honor ignore rules during automation?

Yes, build-graph honors ignore rules to automatically exclude binary files from parsing, ensuring the knowledge graph only contains relevant code structure and relationships from your repository.

What's the best way to maintain codebase context for AI-assisted reviews after a major refactor?

The best way is to run the build-graph workflow for a full rebuild after major refactors, then apply incremental updates thereafter to maintain precise context for AI-assisted code reviews in the evolving repository.