graphify
Skill8 starsChanged 37 days agoMITView on GitHub
Use the graphify knowledge graph to explore architecture, dependencies, and impact before reading or grepping the codebase; keep the graph current with graphify update . after code changes. Use when exploring this repo, answering architecture questions, tracing dependencies, assessing blast radius, or after editing code while graphify-out/ exists.
115 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- ever-works/skillstheir own version, first seen Nov 8, 2026
- rylsherdamz-rgb/stellar-forgetheir own version, first seen Nov 8, 2026
- brebuilds/claude-skillstheir own version, first seen Nov 8, 2026
- GstMirabal/Token-Optimized-Agent-Pipelinetheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
Used with
Projects with it also use remotion-maps, remotion-saas and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillremotion-maps
Remotion Map animation knowledge
Also in 4 projects that use this
OpenAISkillremotion-saas
Build an app with Remotion
Also in 4 projects that use this
royaluniondesign-sysSkilldeployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
Also in 4 projects that use this
mstuder-slalomSkilldjango-verification
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
Also in 3 projects that use this
ttmouseSkillprompt-master
提示词主控 - 智能选择合适的领域skill并生成提示词,支持自动领域分类和调度
Also in 4 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 6 projects that use this
Other versions115 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 115
- safishamsi/graphify★ 144ksame name
- Graphify-Labs/graphify★ 144ksame name
- zaxbysauce/opencode-swarm★ 519same name
- ZaxbyHub/opencode-swarm★ 518same name
- nandyalu/trailarr★ 486same name
- bdfinst/agentic-dev-team★ 302same name
- cin12211/orca-q★ 225same name
- sammcj/agentic-coding★ 169same name
- EBISPOT/ols4★ 106same name
- buildomator/buildomator★ 102same name
105 more not listed
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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/adhd-hub.mdcCursor rule
- .cursor/rules/graphify.mdcCursor rule
- adhd-hub-projectsSkill
- adhd-hub-sessionSkill
- env-checkSkill
The file
Files
Graphify
Local knowledge graph for this repo lives in graphify-out/.
CLI (Windows): %USERPROFILE%\.local\bin\graphify.exe — ensure that dir is on PATH, or invoke it by full path.
When to use
| Situation | Command |
| Any architecture / “how does X work?” question | graphify query "<question>" |
| Dependency between two symbols | graphify path "<A>" "<B>" |
| Everything related to a concept | graphify explain "<concept>" |
| Blast radius of a change | graphify affected "<symbol>" |
| Core hubs | graphify god-nodes |
| After editing code | graphify update . |
Before broad exploration with Read/Grep/Glob/Bash, run query / path / explain first (same rule as .cursor/rules/graphify.mdc). Pass this requirement into subagent prompts that explore code.
After modifying code files, always run:
graphify update .AST-only refresh — no API key / LLM cost. Use --force (or GRAPHIFY_FORCE=1) if a refactor deleted a lot of code and the rebuild looks smaller than the old graph.
Workflow
graphify query "..."(orpath/explain) to get a scoped subgraph.- Open only the files/symbols the graph points to.
- Edit.
graphify update .- Optionally
graphify affected "<changed-symbol>"to check fallout.
Navigation artifacts
graphify-out/GRAPH_REPORT.md— communities, god nodes, broad reviewgraphify-out/wiki/index.md— if present, prefer over raw file walks- Default graph:
graphify-out/graph.json
Do not
- Skip graphify because the area “feels familiar”
- Dump the whole
graph.jsoninto chat — use query/path/explain - Forget
graphify update .after code changes (required byAGENTS.md)
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.

