| name | sprang |
| description | Build or refresh the Sprang knowledge graph for this workspace. Use when the user says "/sprang", "build the knowledge graph", "scan the codebase", "index this project", or "run sprang". |
Build or refresh the Sprang knowledge graph for this workspace.
- Check if
.sprang/knowledge-graph.json exists — note its generated_at, phase, and kind (codebase or knowledge).
- Call
sprang_health to show current graph status (if graph exists).
- Decide which analysis to run:
- Source code (
.ts, .py, .go, .rs, etc.) → run /sprang-analyze
- Primarily markdown notes (Obsidian, Logseq, Zettelkasten) → run
/sprang-knowledge
- Both → ask the user which they want
- For codebase analysis → run
npx @faviovazquez/sprang scan . to produce the skeleton graph, then run /sprang-analyze for full enrichment.
- For knowledge base → run
/sprang-knowledge directly.
- Once complete, call
sprang_health to show the new graph summary.
- Report: nodes created, edges, top insights, any warnings flagged.
- Suggest next steps:
/sprang-onboard, /sprang-chat, /sprang-diff, or open dashboard: pnpm --filter @sprang/dashboard dev.
