Unit Testing Debugger
Seth HobsonCommunityCreated by Seth Hobson
- Subagent
- Review and audit
- Software development
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The unit-testing-debugger acts as a specialized agent for root cause analysis in software development. It follows a structured debugging process to identify, isolate, and resolve issues, ensuring that fixes address the underlying problem rather than just the symptoms. By analyzing error logs, stack traces, and code changes, the agent provides comprehensive diagnostic reports including evidence-based explanations, code fixes, and long-term prevention strategies.
What it does
- Captures and analyzes error messages and stack traces.
- Identifies reproduction steps for reported issues.
- Isolates the specific location of code failures.
- Proposes minimal, effective code fixes.
- Verifies the solution and suggests prevention strategies.
When to use it
- When encountering persistent test failures in your codebase.
- When debugging unexpected application behavior or runtime errors.
- When you need a structured approach to root cause analysis.
- When you want to implement long-term fixes to prevent recurring bugs.
Advantages
- Focuses on root cause analysis rather than quick patches.
- Provides clear evidence to support diagnostic conclusions.
- Includes actionable prevention recommendations.
- Standardizes the debugging workflow for consistent results.
Usage examples
- “My unit test for the user authentication module is failing with a null pointer exception. Can you help?”
- The agent will analyze the stack trace, identify the null variable, suggest a code fix to handle the null state, and provide a test case to verify the fix.
- “The application is crashing intermittently during data processing. Here are the logs.”
- The agent will review the logs, hypothesize the cause of the intermittent failure, and suggest strategic logging or code changes to stabilize the process.
Install
Download the subagent as a ZIP:
https://autogineer.com/agent-skills/wshobson/unit-testing-debugger/downloadExtract the subagent file into .claude/agents in your project (use ~/.claude/agents for every project):
mkdir -p .claude/agents && unzip -j unit-testing-debugger.zip 'unit-testing-debugger/debugger.md' -d .claude/agentsKeep 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 AutoGineer967 B
- LICENSELicence file added by AutoGineer1.0 KiB
- debugger.md797 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.
Attribution and licence
- Created by
- Seth Hobson
- Publisher
- Seth Hobson (Community)
- Source
- wshobson/agents · plugins/unit-testing/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 or Seth Hobson.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download unit-testing-debugger.zip