incident-debug

Stars8

Forks2

UpdatedFebruary 16, 2026 at 10:39

Diagnose runtime issues through structured hypothesis-driven debugging.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

bis-code

bis-code/claude-toolkit

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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

/incident-debug

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

Steps

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

More from this repository

same repository

agent-creator

bis-code/claude-toolkit

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

2026-05-298

deep-dive

bis-code/claude-toolkit

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

2026-05-298

bis-code/claude-toolkit

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

2026-05-298

ralph

bis-code/claude-toolkit

Interactive feature builder with subagent delegation and approval gates.

2026-05-298

rule-creator

bis-code/claude-toolkit

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

2026-05-298

skill-creator

bis-code/claude-toolkit

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

2026-05-298

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

/incident-debug

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

Steps

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