build-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
Install
npx skills add https://github.com/tirth8205/code-review-graph --skill build-graphSKILL.md
Build Graph
Build or incrementally update the knowledge graph for this repository.
Steps
- Call
list_graph_stats_tool. Iflast_updatedis null, the graph has never been built. - For a first build, or when the argument is
full, callbuild_or_update_graph_tool(full_rebuild=True). Otherwise callbuild_or_update_graph_tool()for an incremental update. - Report the response:
status(ok,partialorerror) andsummary.
When to Use
- First set-up of a repository, or after a branch switch or large refactor.
- When the graph looks stale. Hooks installed by
code-review-graph installrun an update after each edit and before each commit, so manual builds are rarely needed.
Notes
- The database is
.code-review-graph/graph.dbin the repository root. - Binary files, dependency and build directories, and patterns in
.code-review-graphignoreare skipped. - For the list of supported languages call
get_docs_section_tool(section_name="languages").
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".