graphify
Skill4 starsChanged 43 days agoMITView on GitHub
Query a local code graph of this repository to find where a symbol is defined, what calls or imports it, and how two modules connect across workspaces. Use before a cross-workspace refactor or when tracing an unfamiliar flow. Navigation aid only.
124 other projects use a version of this.
Adopted by
Most recently taken up by
- chrisezedi/claude-skillstheir own version, first seen Nov 16, 2026
- adeiltonpessini/kit-memoria-iatheir own version, first seen Nov 16, 2026
- miratcan/claude-skillstheir own version, first seen Nov 16, 2026
- AlexanderTar/swarmruntheir own version, first seen Nov 16, 2026
- matt-riley/agent-skillstheir own version, first seen Nov 15, 2026
- ezmichaely/make-it-ezytheir own version, first seen Nov 15, 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 versions124 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 124
- safishamsi/graphify★ 148ksame name
- Graphify-Labs/graphify★ 148ksame name
- ZaxbyHub/opencode-swarm★ 531same name
- zaxbysauce/opencode-swarm★ 519same name
- nandyalu/trailarr★ 486same name
- bdfinst/agentic-dev-team★ 302same name
- cin12211/orca-q★ 225same name
- sammcj/agentic-coding★ 169same name
- EBISPOT/ols4★ 108same name
- buildomator/buildomator★ 102same name
114 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 repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 122 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Always go through the script.
“Common” is measured: kept by at least 6 in 10 of the 122 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Graphify (repository maintenance)
A pinned, code-only Graphify graph of this repository, built by
scripts/graphify.sh into an external cache. It makes no model calls and
writes nothing into the checkout.
scripts/graphify.sh refresh # build, or update after edits/pulls
scripts/graphify.sh query "<terms>" --budget 1500 # nodes related to the terms
scripts/graphify.sh path "<from>" "<to>" # how two symbols connect
scripts/graphify.sh explain "<symbol>" # one node and its neighboursRules:
- Always go through the script. Do not run
graphify install, the upstream skill, hooks, MCP or semantic extraction: they editAGENTS.md, install hooks and may call a model. - The graph is as fresh as the last
refresh. Refresh after pulling or after edits that move code, before trusting a result. - Results are leads, not proof. Read the source before changing anything, and
use
npm run lint:depsfor the enforced import rules. - Scope is set by
.gitignoreand.graphifyignore. SQL and Terraform are not parsed. - This is not the product's Graphify adapter (
apps/worker/src/tools/graphify.ts, pinned separately). Never change that pin for maintenance reasons.
Upstream: Graphify-Labs/graphify tag v0.9.74
(e10df08877f8819a625a1afa38c3297a31fda296), PyPI graphifyy==0.9.74. To
upgrade, change VERSION in the script and this line together.
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.

