القائمة
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".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Analyze a codebase to produce a rich semantic knowledge graph — file summaries, architecture layers, guided tour, domain map, risk scores. Use when the user says "/sprang-analyze", "analyze the codebase", "full analysis", or "run sprang-analyze".
Analyze a codebase to produce a rich semantic knowledge graph — file summaries, architecture layers, guided tour, domain map, risk scores. Use when the user says "/sprang-analyze", "analyze the codebase", "full analysis", or "run sprang-analyze".
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".
Guided architecture tour for new team members — adapts to junior, senior, or PM persona. Use when the user says "/sprang-onboard", "onboard me", "give me a tour", "I'm new to this codebase", or "walk me through the architecture".
Browse and write team annotations attached to graph nodes — institutional knowledge, decision history, ownership. Use when the user says "/sprang-team", "add annotation", "team knowledge", "who owns this", or "document this decision".
Full structural health report — health grade, code smells, security issues, risk nodes, orphans, circular dependencies. Use when the user says "/sprang-health", "health report", "code smells", "show risks", "what's broken", "security issues", or "architectural health".
| 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". |
.sprang/knowledge-graph.json exists — note its generated_at, phase, and kind (codebase or knowledge)..ts, .py, .go, .rs, etc.) → run /sprang-analyze for full LLM-driven codebase analysis..md, Obsidian vault, Logseq, Zettelkasten) → run /sprang-knowledge for note graph analysis.npx @faviovazquez/sprang scan $ARGUMENTS (use cwd if no args) to produce the skeleton graph (<60s), then follow /sprang-analyze for full enrichment./sprang-knowledge directly — no CLI prerequisite needed..sprang/SPRANG_REPORT.md and display key findings./sprang-onboard (codebase tour), /sprang-chat (ask questions), /sprang-diff (blast radius before commits), or open dashboard with pnpm --filter @sprang/dashboard dev.