skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Coding / Debugging Strategies Skill by @wshobson
The skill is the plugins/developer-essentials/skills/debugging-strategies folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
A methodical approach to tracking down bugs: reproduce, isolate, hypothesise and verify, with profiling and root-cause techniques.
Frames debugging as the scientific method, from a reproduction checklist through tools and mindset habits. Applies across languages, covering crashes, performance problems and production-only failures.
The original SKILL.md is organised into these sections:
Written and maintained by @wshobson. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# Debugging Strategies Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches. ## When to Use This Skill - Tracking down elusive bugs - Investigating performance issues - Understanding unfamiliar codebases - Debugging production issues - Analyzing crash dumps and stack traces - Profiling application performance - Investigating memory leaks - Debugging distributed systems ## Core Principles ### 1. The Scientific Method **1. Observe**: What's the actual behavior? **2. Hypothesize**: What could be causing it? **3. Experiment**: Test your hypothesis **4. Analyze**: Did it prove/disprove your theory? **5. Repeat**: Until you find the root cause ### 2. Debugging Mindset **Don't Assume:** - "It can't be X" - Yes it can - "I didn't change Y" - Check anyway - "It works on my machine" - Find out why **Do:** - Reproduce consistently - Isolate the problem - Keep detailed notes …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.