graphify
Skill0 starsChanged 5 days agoApache-2.0View on GitHub
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
- Reads credentials
124 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- chrisezedi/claude-skillstheir 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
- lunox-work/sandbox-factorytheir own version, first seen Nov 16, 2026
- matt-riley/agent-skillsedited, 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 · 2
- matt-riley/agent-skills★ 317% same
- aayushus/skills★ 111% same
Wrote their own version · 122
- safishamsi/graphify★ 148ksame name
- Graphify-Labs/graphify★ 148ksame name
- zaxbysauce/opencode-swarm★ 532same name
- ZaxbyHub/opencode-swarm★ 531same 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
112 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 repository12 other files it gives its agents.
- busca-eficienteSkill
- docs-context7Skill
- grillingSkill
- licao-aprendidaSkill
- prSkill
- rememberSkill
- sem-cara-de-iaSkill
- skill-smithSkill
- spec-primeiroSkill
- veracidade-de-numeroSkill
- verifySkill
- wizardSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 122 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 50
If the graphify CLI is unavailable, fall back to the inline NetworkX traversal in query.md.
- Very specific: line 65
Before running any subcommand (--update, --cluster-only, query, path, explain, add), check that .graphify_python exists.
- Very specific: line 81
Every bash block in the references uses $(cat graphify-out/.graphify_python) as the interpreter.
- Distinctive: line 85
Never invent an edge. If unsure, use AMBIGUOUS.
- Distinctive: line 86
Never skip the corpus check warning.
- Distinctive: line 87
Always show token cost in the report.
- Distinctive: line 88
Never hide cohesion scores behind symbols - show the raw number.
- Distinctive: line 89
Never run HTML viz on a graph with more than 5,000 nodes without warning the user.
“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
Versão enxuta da skill do graphify (MIT, Copyright (c) 2026 Safi Shamsi; texto em
LICENSES/MIT-graphify.txtna raiz do kit).
/graphify
Turn any folder of files (code, docs, papers, images, video) into a navigable knowledge graph: community detection, an honest audit trail (EXTRACTED/INFERRED/AMBIGUOUS), and three outputs — interactive HTML, GraphRAG-ready JSON, and a plain-language GRAPH_REPORT.md. Persistent across sessions.
This file is the core. Anything not here lives in references/ — see the map at the bottom and load only the one file you need.
Decide first: graph or grep?
| Question shape | Tool |
| "what breaks if I change X", "who depends on X", "how does A reach B", "what are the hubs", broad orientation in an unfamiliar area | the graph (commands below) |
| "where is X", exact string/symbol lookup | rg |
| structural code pattern ("every call passing Y") | ast-grep |
Topology → graph. Text → rg. Never rebuild a graph to answer a text question.
Fast path — existing graph (check this before anything else)
Check whether graphify-out/graph.json exists, relative to the current working directory (the project root where you run commands). If it exists AND the user's request is a natural-language question about the codebase (e.g. "How does X work?", "What calls Y?", "Trace the data flow through Z") and NOT an explicit rebuild command (--update, --cluster-only, or a bare path/URL that implies fresh extraction): skip the build pipeline entirely and run graphify query "<question>" immediately (full flow: references/query.md). Do not run detect. Do not check corpus size. Do not ask the user to narrow. The graph is already built — use it.
/graphify --help or -h with no other arguments: print the ## Usage block of references/usage-flags.md verbatim and stop. Run no commands, detect nothing, do not default the path to ..
Anything that really does need a (re)build → references/pipeline-build.md, and follow its steps in order.
Commands
| Goal | Command |
| Answer a question from the graph | graphify query "<question>" — --dfs to trace one chain, --budget N to cap output (default 2000) |
| Impact / reverse dependencies of X | graphify affected "X" [--depth N] [--relation R] |
| How does A reach B | graphify path "A" "B" |
| What is X, and what touches it | graphify explain "X" |
| Architectural hubs | graphify god-nodes [--top N] |
| Refresh the graph after code changes (AST only, no LLM, free) | graphify update . |
| Recluster an existing graph + regenerate report | graphify cluster-only . |
| Build a graph that does not exist yet | full pipeline — references/pipeline-build.md |
Query discipline (details in references/query.md):
- Expand the question against the graph's own vocabulary first (query.md Step 0, REQUIRED). Node matching is case-folded substring + IDF — no stemming, no synonyms, no cross-language. A wording mismatch returns 0 hits and the answer collapses to noise. Pick only tokens that exist in the graph; never invent one.
- Answer using only what the graph output contains, and quote
source_locationwhen citing a fact. If the graph lacks the information, say so — do not hallucinate edges. - Save the answer back (
graphify save-result … --outcome useful|dead_end|corrected) so the next run learns. At the start of graph work,graphify reflect --if-stalethen readgraphify-out/reflections/LESSONS.md. - If the
graphifyCLI is unavailable, fall back to the inline NetworkX traversal in query.md.
Gotchas that break this skill if ignored
- No API key. Ever. graphify does not read
ANTHROPIC_API_KEY/OPENAI_API_KEY. Code is extracted structurally (AST, no LLM, no key), so the common/graphify .on a repo needs nothing. Semantic extraction (docs/papers/images only) uses Gemini ifGEMINI_API_KEY/GOOGLE_API_KEYis already set, otherwise the host agent itself is the LLM. Prompting for, waiting on, or stopping because of a missing key is a misread of this skill. - Semantic subagents must be
subagent_type="general-purpose".Exploreis read-only, cannot write chunk files, and silently drops the extraction. Dispatch every chunk in one message or they run sequentially and the parallelism is lost. - Code-only corpus: skip semantic extraction, but first write the empty
graphify-out/.graphify_semantic.json— the merge reads it unconditionally and otherwise dies withFileNotFoundError. - Substitute the placeholders (
INPUT_PATH,IS_DIRECTED,SPEC_PATH,LABELS_DICT, absoluteCHUNK_PATH) in every block.SPEC_PATHmust be the same absolute path in the cache-check and cache-save steps, or entries are written where the next run will not look (#1939). - Never clobber a good graph. An empty extraction aborts before any write, and
to_jsonrefuses to shrinkgraph.json(#479) — re-run with--forceonly when the shrink is intentional (files were deleted). cluster-onlyis self-contained — it regenerates report/json/html by itself. Do not re-run the later pipeline steps after it; they read intermediates that cleanup already deleted.- HTML viz above 5,000 nodes: warn the user first (the exporter auto-aggregates to a community view).
--obsidianonly when explicitly asked — it writes one file per node.
Interpreter guard for subcommands
Before running any subcommand (--update, --cluster-only, query, path, explain, add), check that .graphify_python exists. If it's missing (e.g. user deleted graphify-out/), re-resolve the interpreter first:
if [ ! -f graphify-out/.graphify_python ]; then
GRAPHIFY_BIN=$(which graphify 2>/dev/null)
if [ -n "$GRAPHIFY_BIN" ]; then
PYTHON=$(head -1 "$GRAPHIFY_BIN" | tr -d '#!')
case "$PYTHON" in *[!a-zA-Z0-9/_.@-]*) PYTHON="python3" ;; esac
else
PYTHON="python3"
fi
mkdir -p graphify-out
"$PYTHON" -c "import sys; open('graphify-out/.graphify_python', 'w', encoding='utf-8').write(sys.executable)"
fiEvery bash block in the references uses $(cat graphify-out/.graphify_python) as the interpreter.
Honesty Rules
- Never invent an edge. If unsure, use AMBIGUOUS.
- Never skip the corpus check warning.
- Always show token cost in the report.
- Never hide cohesion scores behind symbols - show the raw number.
- Never run HTML viz on a graph with more than 5,000 nodes without warning the user.
Reference map — load only what the task needs
| Topic | File |
Full command/flag list, --help output, CLI surface beyond the slash command | references/usage-flags.md |
| Full build pipeline Steps 0-9: install + interpreter detection, file detection, AST + semantic extraction, build/cluster/analyze, graph health check, community labels, HTML/Obsidian, manifest + cost + cleanup + final report | references/pipeline-build.md |
query / path / explain: vocabulary expansion, BFS vs DFS, --budget, inline NetworkX fallback, save-result feedback loop, LESSONS.md | references/query.md |
--update (incremental re-extraction, pruning, graph diff) and --cluster-only | references/update.md |
| Exact extraction subagent prompt: JSON schema, node-ID rules, confidence rubric, frontmatter, hyperedges, vision rules | references/extraction-spec.md |
| Exports and benchmark: wiki, Neo4j, FalkorDB, SVG, GraphML, MCP server, token-reduction benchmark | references/exports.md |
| GitHub URL clone, cross-repo merge, monorepo flow | references/github-and-merge.md |
| Video/audio transcription (Whisper) before extraction | references/transcribe.md |
/graphify add <url> and --watch | references/add-watch.md |
| post-commit auto-rebuild hook, native CLAUDE.md integration | references/hooks.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.

