debugging · siviter-xyz — Claude Code skill: what it does, how to install
debugging is a Claude Code skill that guides root cause analysis for errors and test failures. It helps localize bugs and prepare minimal, verified fixes.
MIT 151 installs ★ 22 updated 2026-03-21
npx skills add siviter-xyz/dot-agent --skill debugging -a claude-codeWhat debugging does
This skill guides the agent through a six-step diagnostic sequence whenever exceptions or unexpected states occur. The model gathers logs, builds a reproduction case, tests hypotheses, and applies the smallest viable patch.
The protocol relies on temporary debug logs at state transitions or external API boundaries, requiring their cleanup once solved. It blocks unverified changes: code modifications must remain atomic and require explicit developer confirmation before any commit.
What it helps with
- isolate root causes from stack traces and logs
- insert strategic debug logging around state transitions
- reproduce test failures with minimal test cases
- verify bug fixes without altering unaffected code
Example prompts for the agent
- Investigate this stack trace and find the root cause
- Add debug logging to trace state corruption in the payment flow
- Help reproduce and fix this intermittent test failure
How to install debugging
1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill debugging -a claude-code2Manually: put the files in place
~/.claude/skills/debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/debugging/
1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill debugging -a codex2Manually: put the files in place
.agents/skills/debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill debugging -a cursor2Manually: put the files in place
.cursor/skills/debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install siviter-xyz/dot-agent skills/debugging2Manually: put the files in place
.github/skills/debugging/SKILL.md1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/siviter-xyz/dot-agent --path skills/debuggingManually: put the files in place
.devin/skills/debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about debugging
How to install debugging in Claude Code?
Run npx skills add siviter-xyz/dot-agent --skill debugging -a claude-code in your terminal. You can also place the file directly at ~/.claude/skills/debugging/SKILL.md.
What does the debugging skill do?
It directs the model through structured troubleshooting, from capturing error logs and isolating failure locations to applying atomic bug fixes.
What happens after the fix is implemented?
The agent verifies CI results, groups changes with tests atomically, and asks for user confirmation before suggesting a commit.
Source text
SKILL.md · MIT
--- name: debugging description: Root cause analysis and debugging protocols. Use when encountering errors, test failures, unexpected behavior, stack traces, or when code behaves differently than expected. --- # Debugging Systematic approach to root cause analysis and debugging. ## When to Use - Encountering errors or exceptions - Test failures that need investigation - Unexpected behavior in code - Stack traces or error messages - Code behaving differently than expected - Performance issues or bugs ## Core Principles - **Evidence-based**: Base diagnosis on error messages, logs, and reproducible steps - **Systematic**: Follow structured debugging process - **Minimal fixes**: Implement smallest change that resolves issue - **Verify solutions**: Confirm fix works and doesn't introduce regressions ## Debugging Process Follow systematic debugging process: 1. Capture error information (message, stack trace, logs, environment) 2. Identify reproduction steps (minimal steps, conditions, edge cases) 3. Isolate failure location (function/module, recent changes, dependencies) 4. Form and test hypotheses (evidence-based, systematic testing, debug logging) 5. Implement minimal fix (smallest change, preserve behavior, follow patterns) 6. Verify solution (issue resolved, no regressions, tests pass) See `references/root-cause-analysis.md` for detailed methods. ## Strategic Debug Logging Add debug logging to entry/exit points, state transitions, conditional branches, external API calls, and data transformations. Remove after issue resolved unless it provides ongoing value. ## Error Pattern Recognition Common patterns: null/undefined errors, type errors, timing issues, state corruption, configuration issues. See `references/error-patterns.md` for detailed patterns and solutions. ## Integration After fixing: - Verify CI passes (types, tests, lint) - Stage atomic changes (fix + tests) - Suggest semantic commit message - Confirm with user before committing ## References For detailed guidance, see: - `references/root-cause-analysis.md` - Systematic analysis methods - `references/error-patterns.md` - Common error patterns and solutions - `references/debugging-tools.md` - Debugging tools and techniques
© siviter-xyz · MIT · siviter-xyz/dot-agent
Similar skills
All skills for Testing and QA →debugging by other authors comes first.