incident-debug

스타8

포크2

업데이트2026년 2월 16일 10:39

Diagnose runtime issues through structured hypothesis-driven debugging.

설치

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

출처

bis-code

bis-code/claude-toolkit

다운로드

/incident-debug

Spawns the incident-debugger agent to systematically diagnose runtime or production issues.

Gather context — collect information about the incident:
- If arguments are provided (error messages, log snippets, stack traces), pass those directly
- Otherwise, ask the user for: symptoms, reproduction steps, and when it started
- Run git log --oneline -20 to identify recent changes that may be related
Spawn the agent — use the Task tool:
```
Task tool with subagent_type="incident-debugger"
```
Pass in the prompt:
- All symptom information (error messages, stack traces, logs)
- Recent git changes and affected files
- The project's language, framework, and runtime context
Present findings — relay the agent's diagnosis:
- Show the ranked hypotheses with evidence for/against each
- Present the confirmed root cause with the code path
- Show the proposed fix and regression test
Offer follow-up actions:
- "Apply fix?" — implement the proposed minimal fix
- "Run tests?" — verify the fix and check for regressions
- "Create issue for systemic problems?" — track broader issues as GitHub issues

이 저장소의 다른 Skills

같은 저장소

Interactive agent builder: guides the user through defining a new agent as a behavioral spec, then generates the agent .md and installs it.

Cross-repo investigation: research planning issues, break down into sub-issues, generate ralph session prompts per repo.

Three-phase QA orchestrator: parallel scan, interactive triage, guided fix.

Interactive feature builder with subagent delegation and approval gates.

Interactive rule builder: guides the user through defining a new rule as a constraint doc, then generates the rule .md and installs it.

Interactive skill builder: guides the user through defining a new skill as a structured SOP, then generates the SKILL.md and installs it.

name	incident-debug
description	Diagnose runtime issues through structured hypothesis-driven debugging.

Spawns the incident-debugger agent to systematically diagnose runtime or production issues.

Gather context — collect information about the incident:
- If arguments are provided (error messages, log snippets, stack traces), pass those directly
- Otherwise, ask the user for: symptoms, reproduction steps, and when it started
- Run git log --oneline -20 to identify recent changes that may be related
Spawn the agent — use the Task tool:
```
Task tool with subagent_type="incident-debugger"
```
Pass in the prompt:
- All symptom information (error messages, stack traces, logs)
- Recent git changes and affected files
- The project's language, framework, and runtime context
Present findings — relay the agent's diagnosis:
- Show the ranked hypotheses with evidence for/against each
- Present the confirmed root cause with the code path
- Show the proposed fix and regression test
Offer follow-up actions:
- "Apply fix?" — implement the proposed minimal fix
- "Run tests?" — verify the fix and check for regressions
- "Create issue for systemic problems?" — track broader issues as GitHub issues