build-graph
Skill76 starsChanged 7 months agoApache-2.0View on GitHub
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If the graph has never been built (last_updated is null), proceed with a full build.
- Distinctive: line 15
If the graph exists, proceed with an incremental update.
- Distinctive: line 30
After major refactoring or branch switches
- Distinctive: line 31
If the graph seems stale or out of sync
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build Graph
Build or incrementally update the persistent code knowledge graph for this repository.
Steps
- Check graph status by calling
graphwithaction="stats".- 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.
- Build the graph by calling
graph:- For first-time setup:
graph(action="build", full_rebuild=True) - For updates:
graph(action="update")(incremental by default)
- For first-time setup:
- Verify by calling
graph(action="stats")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, Go, Rust, Java, C#, Ruby, Kotlin, Swift, PHP, C/C++
Other versions3 projects use a version of this.
Word for word · 1
- n24q02m/crg★ 76100% same
Edited · 1
- tirth8205/code-review-graph★ 32k26% same
Wrote their own version · 1
- exactbee/claude-code-workflow★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- review-deltaSkill
- review-prSkill
- impact-auditSkill
- onboard-repoSkill
- refactor-checkSkill
- review-deltaSkill
- review-prSkill
- security-sweepSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.