skills.rest
mcouthon
mcouthonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Identify, reproduce, and resolve bugs using a hypothesis-driven debugging process.

77|11|Updated Dec 26, 2025
Search Tags:#testing#debugging#investigation#hypothesis#root-cause#reproduction#bug-fix
One-click install
npx skills add https://github.com/mcouthon/agents --skill debug-mcouthon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/mcouthon/agents/tree/main/.github/skills/debug
Command: npx skills add https://github.com/mcouthon/agents --skill debug-mcouthon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging with a hypothesis-driven approach to identify, reproduce, and fix issues efficiently, reducing guesswork and wasted time.

Core Features & Use Cases

  • Four-phase debugging process: Assessment, Investigation, Resolution, and Quality to structure problem-solving and ensure traceable fixes.
  • Hypothesis Template and Debug Report Format to document reasoning, experiments, and results.
  • Reproduction and Root Cause analysis guidance to isolate failures and verify fixes.
  • Clear guardrails and safety checks to prevent premature or risky changes.

Quick Start

Describe the failing behavior concisely and start the hypothesis-driven debug workflow.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I fix intermittent errors using a hypothesis-driven debugging workflow?▼

Hypothesis-driven debugging fixes intermittent errors by guiding you through Assessment, Investigation, Resolution, and Quality phases to reproduce failures, document experiments, and isolate root causes systematically.

What is the best way to reproduce bugs across development and CI environments?▼

Reproducing bugs across development and CI environments requires a structured investigation phase to isolate failures, document reasoning in a hypothesis template, and verify the exact conditions triggering unexpected behavior.

How do I stop guessing and find the root cause of failing tests?▼

Finding the root cause of failing tests requires a hypothesis-driven approach that replaces guesswork with documented experiments, standardized debug reports, and structured reproduction steps to ensure traceable fixes.

Can I use a structured debugging process for unexpected behavior in my codebase?▼

Yes, a structured debugging process applies to codebases with unexpected behavior, using clear guardrails and safety checks to prevent premature or risky changes while guiding you from initial assessment to verified resolution.

What should be included in a debug report when investigating a bug fix?▼

A debug report for investigating a bug fix should include your documented reasoning, hypothesis experiments, reproduction steps, and root cause analysis results to ensure the resolution is traceable and verified.

Related Skills

Explore More Software Engineering Skills→
0xHarbs0xHarbs
1

debug

Diagnose failures by applying hypothesis-driven root-cause analysis to test outputs, stack traces, and CI logs.

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

gstack-openclaw-investigate

Enforce root cause investigation before applying bug fixes in software debugging.

Community
Advanced
Donaldshen27Donaldshen27

systematic-debugging

Identify bug root causes through a four-phase systematic debugging framework.

Community
Advanced
xxihxxih
1

systematic-debugging

Identify root causes of bugs through a four-stage systematic process.

Community
Intermediate