incident-debug
Skill8 starsChanged 6 months agoMITView on GitHub
Diagnose runtime issues through structured hypothesis-driven debugging.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- nseney1/Soma-Governancetheir own version, first seen Nov 1, 2026
- nseney1/Aegis-Guardrailstheir own version, first seen Oct 25, 2026
- gclm/super-stacktheir own version, first seen Mar 29, 2026
- GA14-hub/claude-code-kit-jatheir own version, first seen Feb 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- nseney1/Aegis-Guardrails★ 4same name
- nseney1/Soma-Governance★ 4same name
- GA14-hub/claude-code-kit-ja★ 1same name
- gclm/super-stack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- .claude/rules/common/agents.mdAGENTS.md
- agent-creatorSkill
- architect-reviewSkill
- build-fixSkill
- code-reviewSkill
- deep-diveSkill
- docsSkill
- performance-reviewSkill
- planSkill
- qaSkill
- ralphSkill
- refactor-cleanSkill
- rule-creatorSkill
- security-reviewSkill
- skill-creatorSkill
- tdd-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
If arguments are provided (error messages, log snippets, stack traces), pass those directly
- Distinctive: line 15
Run git log --oneline -20 to identify recent changes that may be related
- Distinctive: line 22
All symptom information (error messages, stack traces, logs)
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/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 -20to identify recent changes that may be related
- Spawn the agent — use the Task tool:
Pass in the prompt:Task tool with subagent_type="incident-debugger"- 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.