build-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
Works with
--- name: build-graph description: Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically. license: MIT --- # 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-graphignore` are skipped - Supported languages: Python, TypeScript/JavaScript, Vue, Go, Rust, Java, Scala, C#, Ruby, Kotlin, Swift, PHP, Solidity, C/C++
More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
