AutoGineer
Generated banner for Incident Response Debugger
Generated logo for Incident Response Debugger

Incident Response Debugger

Seth HobsonCommunityCreated by Seth Hobson

  • Subagent
  • Research and analysis
  • Software development
  • MIT
  • No issues found
Download ZIP

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

  1. Download the subagent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/wshobson/incident-response-debugger/download

  2. 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

  3. 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

  1. Review error context and form initial hypotheses

  2. Trace the code execution path from entry point to failure

  3. Track variable states at key decision points

  4. Use git bisect to identify the introducing commit when applicable

  5. Analyze dependencies and configuration for drift

  6. Isolate the exact failure mechanism

  7. Propose fix strategies with tradeoffs

  8. Document findings in structured format for the next phase

Files

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.

Attribution and licence

Created by
Seth Hobson
Publisher
Seth Hobson (Community)
Source
wshobson/agents · plugins/incident-response/agents/debugger.md · commit 4bde316
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Seth Hobson.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download incident-response-debugger.zip