debug

Reproduce, isolate, and fix software bugs with a structured debugging workflow.

Updated Jun 1, 2025
One-click install
npx skills add https://github.com/Yokhan/yokhanFitnessDocsWebsite --skill debug-yokhan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Yokhan/yokhanFitnessDocsWebsite/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/Yokhan/yokhanFitnessDocsWebsite --skill debug-yokhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a structured, repeatable approach to debugging that guides teams through reproducing issues, isolating causes, validating fixes, and documenting outcomes to improve code quality.

Core Features & Use Cases

  • Reproduce bugs with minimal, verifiable steps.
  • Isolate root causes by tracing execution and changes.
  • Verify fixes with tests and regression checks across projects.

Quick Start

Start a reproducible debugging session by following the outlined steps to reproduce, isolate, hypothesize, fix, verify, and document.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to systematically reproduce and isolate a software bug?

Systematic debugging reproduces and isolates software bugs by tracing execution paths and creating minimal reproductions. This structured approach ensures you identify the exact root cause before attempting any code fixes.

How do I structure a debugging workflow to fix code and prevent regressions?

A structured debugging workflow guides you through defined steps: reproduce, isolate, hypothesize, fix, verify, and document. You validate your code fixes using regression testing before committing the final changes.

Can I apply a structured debugging process to codebases of varying languages and sizes?

Yes, this structured debugging process applies to codebases of varying languages and project sizes. It guides teams through reproducing issues, isolating causes, and validating fixes regardless of the specific technical environment.

Why do I need to create minimal reproductions and document outcomes when fixing bugs?

Creating minimal reproductions and documenting outcomes improves overall code quality by providing verifiable steps to reproduce issues. This disciplined process ensures fixes are validated with tests and logged for future reference.

What should I do if my regression testing fails after applying a code fix?

If regression testing fails after applying a code fix, you must revisit the isolation and hypothesis stages of your debugging workflow. Re-trace the execution path to verify the root cause and validate the corrected fix.