graphify-this-project

Set up a committed graphify knowledge graph with AST extraction, community labeling, and refresh hooks for a project.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill graphify-this-project-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: graphify-this-project
Source: https://github.com/bravros/bravros/tree/main/plugins/tools/skills/graphify-this-project
Command: npx skills add https://github.com/bravros/bravros --skill graphify-this-project-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphifyy, datasketch, rapidfuzz, openai, and includes scripts (resource) and references (resource) components.

What problem does it solve? Codebases are hard to navigate with grep alone, and ad-hoc knowledge graphs drift out of sync or get overwritten when machines run different tool versions. This Skill performs an end-to-end graphify setup for the current project: it extracts an AST-based knowledge graph, labels communities semantically, commits the graph into the repo so it travels via git pull, and installs refresh hooks and a union-merge driver to keep it consistent. ## Core Features & Use Cases - In-project committed graph: Builds graphify-out/graph.json inside the repo with .gitignore surgery so the graph is tracked and shared across machines. - Two refresh tiers: A free hook-driven AST structure rebuild on post-merge, plus an on-demand paid DeepSeek semantic pass that re-derives edges and community labels. - Version pinning and dedup patching: Installs a pinned graphifyy build via uv and applies a vendored dedup fix on pre-0.9 versions so all machines produce structurally identical graphs. - MCP query surface: Registers a user-scoped graphify MCP server for graph-first code questions, with the CLI as backup. - Use Case: After cloning a large Laravel monorepo, run the skill to generate a labeled knowledge graph, then ask "how does the order lifecycle work" and get an answer from the graph instead of running five greps. ## Quick Start Ask the agent to run /graphify-this-project to set up the graphify knowledge graph for the current repository.

Frequently Asked Questions about graphify-this-project

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

FAQPage Schema
How do I set up a knowledge graph for my codebase?▼

Run /graphify-this-project in the project root. It installs a pinned graphifyy build, extracts AST structure, labels communities via an LLM pass, commits graphify-out/graph.json to the repo, and installs post-merge refresh hooks.

How do I keep a code knowledge graph in sync across machines?▼

Commit graphify-out/graph.json to the repo so it travels via git pull, and install the tracked post-merge hook that rebuilds AST structure automatically. All machines must run the same pinned graphifyy version or they overwrite each other's graph.

What is the difference between the structure refresh and the semantic refresh?▼

The structure refresh is a free, hook-driven AST rebuild triggered on git merge with no LLM involved. The semantic refresh is an on-demand paid DeepSeek pass that re-derives semantic edges and community labels, and should be re-run after big refactors.

Can I use graphify without an LLM API key?▼

Yes. The ast-only-extract.py script runs graphify's detect and AST extraction directly without any backend, producing deterministic nodes and edges. Semantic enrichment and community labeling are the only steps that require an LLM.

Why does my graph show collapsed nodes like a single handle() method?▼

Pre-0.9 graphify versions keyed deduplication on label only, collapsing same-named methods across classes into fake god nodes. The skill's apply-dedup-fix.sh patches this on old versions; graphifyy 0.9 and later include the upstream fix.

When should I not use the graph and just grep instead?▼

Use grep when you need an exact string or regex match in source, and skip the graph for runtime behavior, logs, or database state since graphify is static analysis only. If the graph seems stale, pull on the autocommit branch to trigger the refresh hook.