Incident Response Debugger — Agent Skill by Seth Hobson

From the author

Performs deep root cause analysis through code path tracing, git bisect automation, dependency analysis, and systematic hypothesis testing for production bugs.

— the description by Seth Hobson

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The incident-response-debugger is a specialized agent skill designed to perform rigorous root cause analysis on production issues. It employs a structured methodology that combines code path tracing, dependency evaluation, and automated git bisecting to isolate failure mechanisms. By systematically testing hypotheses and inspecting state, it helps developers move from error symptoms to the underlying source of the problem, providing clear fix strategies with associated tradeoffs.

What it does

Traces code execution paths from entry points to failure locations.
Automates git bisect processes to pinpoint the exact commit introducing a bug.
Analyzes dependencies for version conflicts and configuration drift.
Inspects database, cache, and external API states to identify inconsistencies.
Formulates and tests hypotheses regarding failure mechanisms like race conditions or type mismatches.
Generates structured reports outlining findings and potential fix strategies.

When to use it

When you need to identify the root cause of a complex production bug.
When a regression has been introduced and you need to find the specific commit.
When investigating intermittent failures or race conditions.
When you suspect dependency issues or configuration drift are causing system instability.

Advantages

Provides a methodical, evidence-based approach to debugging.
Reduces time spent manually tracing complex code paths.
Offers clear tradeoffs between quick fixes and long-term architectural solutions.
Standardizes the documentation of incident findings.

Usage examples

“I have a 500 error on the checkout page. Here are the logs. Can you trace the path?”: The agent will analyze the provided logs, trace the execution flow through the checkout service, and identify the specific function or state causing the exception.
“Our production build started failing today. Use git bisect to find the bad commit.”: The agent will guide or execute the git bisect process across the repository history to isolate the commit that introduced the breaking change.

Install

Download the subagent as a ZIP:
https://mp-staging.autogineer.com/agent-skills/wshobson/incident-response-debugger/download

Extract the subagent file into .claude/agents in your project (use ~/.claude/agents for every project):

mkdir -p .claude/agents && unzip -j incident-response-debugger.zip 'incident-response-debugger/debugger.md' -d .claude/agents

Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by Seth Hobson

You are a debugging specialist focused on systematic root cause analysis for production issues.

Purpose

Perform deep code analysis and investigation to identify the exact root cause of bugs. You excel at tracing code paths, automating git bisect, analyzing dependencies, and testing hypotheses methodically.

Capabilities

Root cause hypothesis formation with supporting evidence
Code-level analysis: variable states, control flow, timing issues
Git bisect automation: identify the exact introducing commit
Dependency analysis: version conflicts, API changes, configuration drift
State inspection: database state, cache state, external API responses
Failure mechanism identification: race conditions, null checks, type mismatches
Fix strategy options with tradeoffs (quick fix vs proper fix)
Code path tracing from entry point to failure location

Response Approach

Review error context and form initial hypotheses
Trace the code execution path from entry point to failure
Track variable states at key decision points
Use git bisect to identify the introducing commit when applicable
Analyze dependencies and configuration for drift
Isolate the exact failure mechanism
Propose fix strategies with tradeoffs
Document findings in structured format for the next phase

Files

ATTRIBUTION.mdAdded by AutoGineer982 B
LICENSELicence file added by AutoGineer1.0 KiB
debugger.md1.5 KiB

LICENSE

MIT License

Copyright (c) 2024 Seth Hobson

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Requirements and compatibility

Written for: Claude Code

Works with: Claude Code

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Diagnosing Bugs
Matt Pocock· Community
A structured, six-phase discipline for systematically diagnosing and resolving complex software bugs and performance regressions.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository317.5k
Systematic Debugging
Jesse Vincent (obra)· Community
A rigorous, four-phase framework for identifying and resolving technical issues by prioritizing root cause analysis over symptomatic fixes.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository314k
Performance Optimization
Addy Osmani· Community
A rigorous, measurement-first workflow for identifying and fixing performance bottlenecks in frontend and backend applications.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Debugging And Error Recovery
Addy Osmani· Community
A systematic, six-step framework for triaging, reproducing, and resolving software bugs to ensure root-cause fixes.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository113.9k
Animation Performance
Emil Kowalski· Community
A diagnostic guide for identifying and fixing frame drops in web animations to ensure smooth, performant motion.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository54.3k
Parallel Debugging
Seth Hobson· Community
A structured framework for debugging complex issues using parallel hypothesis testing and evidence-based arbitration.
Software developmentClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k