debugging-strategies – Coding skill for AI agents
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
Install the debugging-strategies 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/debugging-strategies-a70ed.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /debugging-strategies – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/debugging-strategies-a70ed.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $debugging-strategies – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/debugging-strategies-a70ed.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /debugging-strategies – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/debugging-strategies-a70ed.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /debugging-strategies – then describe the task you want done.
SKILL.md content
Debugging Strategies
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
Use this skill when
- Tracking down elusive bugs
- Investigating performance issues
- Debugging production incidents
- Analyzing crash dumps or stack traces
- Debugging distributed systems
Do not use this skill when
- There is no reproducible issue or observable symptom
- The task is purely feature development
- You cannot access logs, traces, or runtime signals
Instructions
- Reproduce the issue and capture logs, traces, and environment details.
- Form hypotheses and design controlled experiments.
- Narrow scope with binary search and targeted instrumentation.
- Document findings and verify the fix.
- If detailed playbooks are required, open
resources/implementation-playbook.md.
Resources
resources/implementation-playbook.mdfor detailed debugging patterns and checklists.
Limitations
- 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-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.
- devcontainer-setup – Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go)…
- developer-advocacy – When the user wants to do developer advocacy activities including conference talks, live…
- developer-audience-context – When the user wants to establish or update their developer audience context. Also use…