ed5b54e87e
Bump 0.8.13 -> 0.8.45. Extract the SKILL.md monolith (~530 lines) into references/ for progressive disclosure: github-and-merge, transcribe, extraction-spec, exports, update, query, add-watch, hooks. SKILL.md now points to each reference and loads it only on the path that needs it. Inline fixes carried by the new version: empty-extraction guard before any write (#1392), shrink-guard ordering so GRAPH_REPORT/analysis never describe a graph.json that was refused (#479), root= relativization for build/manifest parity across clones (#1361/#1417), stale-cache cleanup and code-only semantic pre-write (#1392), edge-direction preserving merge (#801). Adds FalkorDB export (--falkordb/--falkordb-push) and rewrites the frontmatter description (drops the obsolete trigger: field). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0169vjUD1sP9Nx4ZiCa8wvAw
47 lines
2.1 KiB
Markdown
47 lines
2.1 KiB
Markdown
# graphify reference: GitHub clone and cross-repo merge
|
|
|
|
Load this when the user passed one or more `https://github.com/...` URLs, or named several local subfolders to merge into one graph.
|
|
|
|
### Step 0 - Clone GitHub repo(s) (only if a GitHub URL was given)
|
|
|
|
**Single repo:**
|
|
```bash
|
|
LOCAL_PATH=$(graphify clone <github-url> [--branch <branch>])
|
|
# Use LOCAL_PATH as the target for all subsequent steps
|
|
```
|
|
|
|
**Multiple repos (cross-repo graph):**
|
|
```bash
|
|
# Clone each repo, run the full pipeline on each, then merge
|
|
graphify clone <url1> # → ~/.graphify/repos/<owner1>/<repo1>
|
|
graphify clone <url2> # → ~/.graphify/repos/<owner2>/<repo2>
|
|
# Run /graphify on each local path to produce their graph.json files
|
|
# Then merge:
|
|
graphify merge-graphs \
|
|
~/.graphify/repos/<owner1>/<repo1>/graphify-out/graph.json \
|
|
~/.graphify/repos/<owner2>/<repo2>/graphify-out/graph.json \
|
|
--out graphify-out/cross-repo-graph.json
|
|
```
|
|
|
|
Graphify clones into `~/.graphify/repos/<owner>/<repo>` and reuses existing clones on repeat runs. Each node in the merged graph carries a `repo` attribute so you can filter by origin.
|
|
|
|
**Multiple local subfolders (monorepo or multi-service layout):**
|
|
|
|
The skill pipeline writes all intermediate and final outputs to `graphify-out/` in the current working directory. Running the skill on each subfolder separately will clobber the same output dir. Instead, use the CLI directly for each subfolder — it places `graphify-out/` *inside* the scanned path:
|
|
|
|
```bash
|
|
graphify extract ./core/ # → ./core/graphify-out/graph.json
|
|
graphify extract ./service/ # → ./service/graphify-out/graph.json
|
|
graphify extract ./platform/ # → ./platform/graphify-out/graph.json
|
|
# Add --backend gemini|kimi|openai|deepseek|claude-cli depending on which API key you have set
|
|
|
|
# Then merge at the project root:
|
|
graphify merge-graphs \
|
|
./core/graphify-out/graph.json \
|
|
./service/graphify-out/graph.json \
|
|
./platform/graphify-out/graph.json \
|
|
--out graphify-out/graph.json
|
|
```
|
|
|
|
Once `graphify-out/graph.json` exists, the fast path above takes over: any codebase question runs `graphify query` directly on the merged graph — no re-extraction, no size gate.
|