Error Diagnostics Debugger — Agent Skill by Seth Hobson

From the author

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

— the description by Seth Hobson

AutoGineer summary

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

The error-diagnostics-debugger skill provides a structured, expert-led approach to troubleshooting software issues. It guides the user through a rigorous process of capturing error data, isolating failure points, and verifying solutions. By focusing on root cause analysis rather than superficial symptom management, the skill ensures that fixes are robust and accompanied by long-term prevention strategies.

What it does

Analyzes error messages, stack traces, and system logs to identify failure points.
Assists in reproducing issues to confirm the scope of the bug.
Formulates and tests hypotheses regarding the underlying cause of unexpected behavior.
Provides specific, minimal code fixes to resolve identified issues.
Suggests testing approaches and prevention strategies to avoid future regressions.

When to use it

When encountering persistent errors or unexpected application behavior.
During the investigation of failed automated tests.
When you need a structured methodology to isolate complex bugs.
When you want to ensure that a fix addresses the root cause rather than just the symptom.

Advantages

Promotes a disciplined, evidence-based approach to debugging.
Reduces time spent on trial-and-error by focusing on hypothesis testing.
Encourages the implementation of strategic logging for better visibility.
Provides actionable prevention recommendations to improve code quality.

Usage examples

“I am getting a null pointer exception in my backend service, here is the stack trace.”: The agent will analyze the stack trace, identify the specific line causing the error, explain why the null value occurs, and provide a code fix to handle the state safely.
“My unit tests are failing after the latest refactor, can you help me debug?”: The agent will compare the current code against the test requirements, isolate the logic change that caused the failure, and suggest a fix to restore expected functionality.

Install

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

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

mkdir -p .claude/agents && unzip -j error-diagnostics-debugger.zip 'error-diagnostics-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 an expert debugger specializing in root cause analysis.

When invoked:

Capture error message and stack trace
Identify reproduction steps
Isolate the failure location
Implement minimal fix
Verify solution works

Debugging process:

Analyze error messages and logs
Check recent code changes
Form and test hypotheses
Add strategic debug logging
Inspect variable states

For each issue, provide:

Root cause explanation
Evidence supporting the diagnosis
Specific code fix
Testing approach
Prevention recommendations

Focus on fixing the underlying issue, not just symptoms.

Files

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

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