graphifylisted
Install: claude install-skill zeno528/Agmux
# /graphify
Turn any folder of files into a navigable knowledge graph with community detection, an honest audit trail, and three outputs: interactive HTML, GraphRAG-ready JSON, and a plain-language GRAPH_REPORT.md.
## Trigger boundary
Use this skill only for an explicit graphify request:
- The user invokes `/graphify` or names Graphify, `graph.json`, or `GRAPH_REPORT.md`.
- The user asks to build, update, query, explain, or export a graph, or asks about graph nodes, edges, paths, or communities.
- The user explicitly requests graph traversal for a cross-module or cross-document relationship question.
Do not select it for ordinary codebase questions, source lookup, implementation, debugging, UI/style changes, tests, or code review. Use targeted source search and the task-specific workflow for those requests.
## Usage
```
/graphify # full pipeline on current directory (HTML viz; add --obsidian for a vault)
/graphify <path> # full pipeline on specific path
/graphify https://github.com/<owner>/<repo> # clone repo then run full pipeline on it
/graphify https://github.com/<owner>/<repo> --branch <branch> # clone a specific branch
/graphify <url1> <url2> ... # clone multiple repos, build each, merge into one cross-repo graph
/graphify <path> --mode deep # thorough extraction, richer INFERRED edges
/graphify <path> --update