AutoGineer
Generated banner for Incident Response Error Detective
Generated logo for Incident Response Error Detective

Incident Response Error Detective

Seth HobsonCommunityCreated by Seth Hobson

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

From the author

Analyzes error traces, logs, and observability data to identify error signatures, reproduction steps, user impact, and timeline context for production issues.
— the description by Seth Hobson

AutoGineer summary

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

The incident-response-error-detective acts as a specialized diagnostic agent designed to parse complex production error data. By synthesizing information from stack traces, logs, and observability platforms, it helps engineering teams move quickly from raw error signals to actionable insights regarding root causes, user impact, and system-wide cascading effects.

What it does

  • Identifies specific error signatures and failure patterns from logs and traces.
  • Performs deep-dive analysis on stack traces to pinpoint failure locations.
  • Correlates production issues with deployment timelines and configuration changes.
  • Assesses the scope of user impact and business risk associated with an incident.
  • Maps cascading failures across upstream and downstream services.
  • Generates structured findings to guide the next phase of incident investigation.

When to use it

  • When investigating unexplained production errors or system anomalies.
  • During incident response to quickly determine the scope and impact of a failure.
  • When correlating distributed traces with error logs to find root causes.
  • To analyze the relationship between recent deployments and new error spikes.

Advantages

  • Reduces mean time to resolution by automating the synthesis of complex observability data.
  • Provides clear, structured reports that facilitate team communication during incidents.
  • Helps identify hidden patterns in error frequency and distribution.
  • Assists in distinguishing between isolated bugs and systemic cascading failures.

Usage examples

“Analyze these stack traces and logs from our payment service to identify the root cause of the recent 500 errors.”
The agent provides a breakdown of the exception type, identifies the specific failing function, correlates the error with a recent deployment, and estimates the percentage of affected transactions.
“We are seeing a spike in latency and errors in our microservices. Can you correlate these with our recent infrastructure changes?”
The agent maps the error timeline against recent configuration updates and identifies a potential cascading failure originating from a specific downstream service.

Install

  1. Download the subagent as a ZIP:

    https://autogineer.com/agent-skills/wshobson/incident-response-error-detective/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-error-detective.zip 'incident-response-error-detective/error-detective.md' -d .claude/agents

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

Documentation by Seth Hobson

You are an error detection specialist focused on analyzing production errors and observability data.

Purpose

Analyze error traces, stack traces, logs, and monitoring data to build a complete picture of production issues. You excel at identifying error patterns, correlating events across services, and assessing user impact.

Capabilities

  • Error signature analysis: exception types, message patterns, frequency, first occurrence

  • Stack trace deep dive: failure location, call chain, involved components

  • Reproduction step identification: minimal test cases, environment requirements

  • Observability correlation: Sentry/DataDog error groups, distributed traces, APM metrics

  • User impact assessment: affected segments, error rates, business metrics

  • Timeline analysis: deployment correlation, configuration change detection

  • Related symptom identification: cascading failures, upstream/downstream impacts

Response Approach

  1. Analyze the error signature and classify the failure type

  2. Deep-dive into stack traces to identify the failure location and call chain

  3. Correlate with observability data (traces, logs, metrics) for context

  4. Assess user impact and business risk

  5. Build a timeline of when the issue started and what changed

  6. Identify related symptoms and potential cascading effects

  7. Provide structured findings for the next investigation 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/error-detective.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 or Seth Hobson.

Download ZIP

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