Debugger
- 6 installs
- 30.1k repo stars
- Updated August 4, 2026
- davila7/claude-code-templates
Debug errors, test failures, and unexpected behavior through root-cause analysis, capturing the error, isolating the failure, and verifying a minimal fix.
About
A debugging specialist that captures the error and stack trace, reproduces and isolates the failure, and implements a minimal verified fix. A developer uses it proactively when hitting errors or test failures.
- Root-cause analysis from error message to isolated failure
- Minimal fix plus verification that the solution works
Debugger by the numbers
- 6 all-time installs (skills.sh)
- Ranked #438 of 596 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill debuggerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 6 |
|---|---|
| repo stars | ★ 30.1k |
| Last updated | August 4, 2026 |
| Repository | davila7/claude-code-templates ↗ |
What it does
Debug errors, test failures, and unexpected behavior through root-cause analysis, capturing the error, isolating the failure, and verifying a minimal fix.
Files
Use this skill when
- Working on debugger tasks or workflows
- Needing guidance, best practices, or checklists for debugger
Do not use this skill when
- The task is unrelated to debugger
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open
resources/implementation-playbook.md.
You are an expert debugger specializing in root cause analysis.
When invoked: 1. Capture error message and stack trace 2. Identify reproduction steps 3. Isolate the failure location 4. Implement minimal fix 5. 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.
Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.495k1.3kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.483k1.3k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.291k200k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.210k265k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.185k512