원클릭으로 Manus에서 모든 스킬 실행

sprang-chat

스타1

포크1

업데이트2026년 6월 4일 08:48

Ask any question about the codebase using the knowledge graph. Use when the user says "/sprang-chat", "ask about the codebase", "what does X do", or any question about code that should be answered from the knowledge graph.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

FavioVazquez

FavioVazquez/sprang

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

기타 컴퓨터 관련 직업컴퓨터 및 수학직·SOC 15-1299

SKILL.md

readonly

name	sprang-chat
description	Ask any question about the codebase using the knowledge graph. Use when the user says "/sprang-chat", "ask about the codebase", "what does X do", or any question about code that should be answered from the knowledge graph.

Ask any question about the codebase using the knowledge graph.

Answer questions grounded entirely in .sprang/knowledge-graph.json.

Check .sprang/knowledge-graph.json exists. If not, tell the user to run /sprang-analyze first.
Read project metadata (project_name, description, languages) to anchor context.
Call sprang_query with keywords from the question to find relevant nodes — use multiple search terms if needed.
For each matched node, call sprang_node to get its 1-hop neighborhood (in/out degree, layer, neighbors).
Follow edges to trace the dependency chain as far as needed to fully answer.
Find which architectural layers the matched nodes belong to.
Answer grounded in graph data — cite summary fields directly, reference file paths, name layers.
Offer follow-ups: /sprang-explain <file> for deep dive, /sprang-diff if the topic involves recent changes.

$ARGUMENTS

이 저장소의 다른 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

FavioVazquez/sprang

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

name	sprang-chat
description	Ask any question about the codebase using the knowledge graph. Use when the user says "/sprang-chat", "ask about the codebase", "what does X do", or any question about code that should be answered from the knowledge graph.

Ask any question about the codebase using the knowledge graph.

Answer questions grounded entirely in .sprang/knowledge-graph.json.

Check .sprang/knowledge-graph.json exists. If not, tell the user to run /sprang-analyze first.
Read project metadata (project_name, description, languages) to anchor context.
Call sprang_query with keywords from the question to find relevant nodes — use multiple search terms if needed.
For each matched node, call sprang_node to get its 1-hop neighborhood (in/out degree, layer, neighbors).
Follow edges to trace the dependency chain as far as needed to fully answer.
Find which architectural layers the matched nodes belong to.
Answer grounded in graph data — cite summary fields directly, reference file paths, name layers.
Offer follow-ups: /sprang-explain <file> for deep dive, /sprang-diff if the topic involves recent changes.

$ARGUMENTS