debugger – Coding skill for AI agents
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
Install the debugger skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/debugger-9ecc1.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /debugger – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/debugger-9ecc1.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $debugger – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/debugger-9ecc1.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /debugger – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/debugger-9ecc1.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /debugger – then describe the task you want done.
SKILL.md content
Use this skill when
- Reproducing a supplied error, failing test or unexpected application behavior.
- Testing competing root-cause hypotheses before applying a scoped fix.
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.
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.
Example
User request:
> Investigate this failure with @debugger, prove the root cause, implement the smallest safe fix, and verify it.
Limitations
- No local support scripts are bundled. Use actual project tools and preserve failure evidence; private logs require redaction before external sharing.
- Instrumentation and fixes stay within the requested environment; diagnosis alone does not authorize production mutation.
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related skills
- debugging-and-error-recovery – Guides systematic root-cause debugging. Use when tests fail, builds break, behavior…
- debugging-code – Interactively debug source code — set breakpoints, step through execution line by line…
- debugging-strategies – Transform debugging from frustrating guesswork into systematic problem-solving with…
- debugging-toolkit – Use when working with debugging toolkit smart debug (Alias for…
- debugging-toolkit-smart-debug – Diagnose failures from reproduction steps, traces, logs and code; test hypotheses and…
- named-persona-adversarial-review – Code review through the lens of real engineers' documented philosophies (Torvalds…
- deprecation-and-migration – Manages deprecation and migration. Use when removing old systems, APIs, or features. Use…
- simplify-code – Parallel 4-agent cleanup of recent code changes.