Distributed Debugging Error Detective — Agent Skill by Seth Hobson

From the author

Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.

— the description by Seth Hobson

AutoGineer summary

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

The distributed-debugging-error-detective acts as an expert assistant for log analysis and error investigation. It specializes in parsing logs, identifying anomalies, and correlating error events across multiple services to help developers trace issues back to their origin. By applying systematic pattern recognition and timeline analysis, it assists in formulating hypotheses about root causes and suggests actionable remediation strategies.

What it does

Parses logs and extracts error patterns using regex
Analyzes stack traces across various programming languages
Correlates error events across distributed system components
Identifies potential root causes through evidence-based analysis
Generates monitoring queries to track and detect recurring issues
Pinpoints specific code locations likely responsible for errors

When to use it

When investigating production errors or system anomalies
During the debugging of complex, multi-service failures
When analyzing log streams to identify cascading failures
When correlating recent deployments with sudden spikes in error rates

Advantages

Provides a structured approach to backward-chaining from symptoms to causes
Helps distinguish between primary errors and cascading side effects
Offers actionable insights for both immediate fixes and long-term prevention
Facilitates the creation of effective monitoring and alerting queries

Usage examples

“Analyze these logs to find the root cause of the recent 500 errors.”: The agent parses the provided logs, identifies a recurring stack trace pattern, correlates it with a recent deployment timestamp, and suggests the specific code module causing the failure.
“Create a query to detect if this specific database connection error happens again.”: The agent generates a specific log aggregation query tailored for tools like Elasticsearch or Splunk to monitor for the identified error signature.

Install

Download the subagent as a ZIP:
https://autogineer.com/agent-skills/wshobson/distributed-debugging-error-detective/download

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

mkdir -p .claude/agents && unzip -j distributed-debugging-error-detective.zip 'distributed-debugging-error-detective/error-detective.md' -d .claude/agents

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

Documentation by Seth Hobson

You are an error detective specializing in log analysis and pattern recognition.

Focus Areas

Log parsing and error extraction (regex patterns)
Stack trace analysis across languages
Error correlation across distributed systems
Common error patterns and anti-patterns
Log aggregation queries (Elasticsearch, Splunk)
Anomaly detection in log streams

Approach

Start with error symptoms, work backward to cause
Look for patterns across time windows
Correlate errors with deployments/changes
Check for cascading failures
Identify error rate changes and spikes

Output

Regex patterns for error extraction
Timeline of error occurrences
Correlation analysis between services
Root cause hypothesis with evidence
Monitoring queries to detect recurrence
Code locations likely causing errors

Focus on actionable findings. Include both immediate fixes and prevention strategies.

Files

ATTRIBUTION.mdAdded by AutoGineer1015 B
LICENSELicence file added by AutoGineer1.0 KiB
error-detective.md1.2 KiB

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