Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add siviter-xyz/dot-agent --skill debugging -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/debugging/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/debugging/

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.

debugging tursodatabase debugging — a skill for tracking down tursodb bugs: compare bytecode against SQLite, turn on trace logs, run ThreadSanitizer, replay a seed and measure stack use. CX Codex +1 1,300installs debugging mrgoonie Enforces a disciplined debugging methodology that stops guesswork and requires fresh test proof before marking tasks done. CX Codex +1 580installs debugging sentimony debugging enforces root-cause discipline during bug investigations. Prevents the agent from modifying code until it proves why a failure happens. CX Codex +1 2,800installs debugging akillness debugging — a skill that walks the agent through a reproduce → isolate → verify loop for concrete bugs, regressions and flaky failures. Useful once you already have a failing test or request. CX Codex +1 364installs Debugging pluginagentmarketplace A walkthrough of Python debugging: pdb sessions, IDE breakpoints, logging setup, profilers and traceback reading, with the commands spelled out. CX Codex +1 233installs systematic-debugging sammcj systematic-debugging — a structured debugging skill for stubborn bugs that survived several fixes. It traces symptoms to root causes before proposing code changes. CX Codex +1 ★ 173repo stars debug cyrusagents debug works through a reported bug from reproduction to a minimal fix. Use it when you need to trace an error and verify the result. CX Codex +1 871installs Debug Mode Instructions official github Debug Mode Instructions — a GitHub Copilot subagent that walks debugging in phases: reproduce the bug, find the root cause, patch it, verify. Useful when a failure is flaky and you don't know where to start. CX Codex +1 ★ 41,430repo stars rstest-debugging rstackjs rstest-debugging diagnoses Rstest startup, build, runtime, logging, memory, and performance issues with traces and comparable measurements. CX Codex +1 133installs debugging-and-error-recovery addyosmani The debugging-and-error-recovery Claude Code skill traces failures to their root cause and checks the fix. It activates for failing tests, broken builds, unexpected errors, or behavior that no longer matches expectations. CX Codex +1 79,600installs frontend-testing-debugging fcakyon frontend-testing-debugging guides an agent through visual debugging: reproduce the interaction, inspect console and layout, fix the root rule, rerun the journey that broke. CX Codex +1 ★ 1,216repo stars

From the same set11

The whole set →
software-engineer software-engineer — a skill that gives the agent rules for code style, documentation and workflow: no filler comments, no git commits on its own, questions when something is unclear. CX Codex +1 637installs python Gives the agent one set of Python conventions: typing, dependency injection, module and test layout. Useful when edits land in an existing codebase. CX Codex +1 353installs create-agents-md create-agents-md generates repo-committed AGENTS.md files for inline rules. Useful for keeping code style, build commands, and safety boundaries close to the code. CX Codex +1 306installs typescript typescript is a Claude Code skill that sets standards for writing and changing TypeScript. It activates for TypeScript and TypeScript React files. CX Codex +1 239installs cli-building cli-building guides AI agents to build command-line tools using async-first patterns, modular command composition, and terminal formatting with NO_COLOR support. CX Codex +1 201installs semantic-git The semantic-git skill groups related changes into atomic commits and formats messages as Conventional Commits. Use it when an agent is preparing Git changes for commit. CX Codex +1 201installs media-processing media-processing is a Claude Code skill for batch media workflows: resizing images, converting audio, and compressing video with FFmpeg, ImageMagick, and Python scripts. CX Codex +1 151installs psi psi structures development around planning, specifications and test-first implementation. It runs only when the user asks for it or the project’s AGENTS.md mentions it. CX Codex +1 144installs

Project sponsors

Companies that keep this analytics open