ワンクリックでManusで任意のスキルを実行

sprang

スター1

フォーク1

更新日2026年6月17日 18:05

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 ページを確認してインストールできます。

Manusで実行

ソース

FavioVazquez

FavioVazquez/sprang

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ソフトウェア開発者コンピュータ・数学職·SOC 15-1252

SKILL.md

readonly

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".

Check if .sprang/knowledge-graph.json exists — note its generated_at, phase, and kind (codebase or knowledge).
Detect what to analyze:
- If the target directory has source code (.ts, .py, .go, .rs, etc.) → run /sprang-analyze for full LLM-driven codebase analysis.
- If it contains primarily markdown notes (.md, Obsidian vault, Logseq, Zettelkasten) → run /sprang-knowledge for note graph analysis.
- If both → ask the user which they want.
For codebase: run npx @faviovazquez/sprang scan $ARGUMENTS (use cwd if no args) to produce the skeleton graph (<60s), then follow /sprang-analyze for full enrichment.
For knowledge base: follow /sprang-knowledge directly — no CLI prerequisite needed.
Read .sprang/SPRANG_REPORT.md and display key findings.
Report: nodes created, edges, top insights, smells detected (codebase) or top connected notes (knowledge).
Suggest next steps: /sprang-onboard (codebase tour), /sprang-chat (ask questions), /sprang-diff (blast radius before commits), or open dashboard with pnpm --filter @sprang/dashboard dev.

このリポジトリの他の Skills

同じリポジトリ

sprang-analyze

FavioVazquez/sprang

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".

2026-06-171

sprang-onboard

FavioVazquez/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".

2026-06-081

sprang-team

FavioVazquez/sprang

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".

2026-06-081

sprang-health

FavioVazquez/sprang

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".

2026-06-081

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".

Check if .sprang/knowledge-graph.json exists — note its generated_at, phase, and kind (codebase or knowledge).
Detect what to analyze:
- If the target directory has source code (.ts, .py, .go, .rs, etc.) → run /sprang-analyze for full LLM-driven codebase analysis.
- If it contains primarily markdown notes (.md, Obsidian vault, Logseq, Zettelkasten) → run /sprang-knowledge for note graph analysis.
- If both → ask the user which they want.
For codebase: run npx @faviovazquez/sprang scan $ARGUMENTS (use cwd if no args) to produce the skeleton graph (<60s), then follow /sprang-analyze for full enrichment.
For knowledge base: follow /sprang-knowledge directly — no CLI prerequisite needed.
Read .sprang/SPRANG_REPORT.md and display key findings.
Report: nodes created, edges, top insights, smells detected (codebase) or top connected notes (knowledge).
Suggest next steps: /sprang-onboard (codebase tour), /sprang-chat (ask questions), /sprang-diff (blast radius before commits), or open dashboard with pnpm --filter @sprang/dashboard dev.