debugging

Identify and prove bug root causes through a structured five-phase workflow.

41|4|Updated Jan 28, 2026

Search Tags:#testing #debugging #investigation #journal #phases #reproduction #root-cause-analysis

Ready to run

npx skills add https://github.com/etr/groundwork --skill debugging-etr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/etr/groundwork/tree/main/skills/debugging
Command: npx skills add https://github.com/etr/groundwork --skill debugging-etr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The debugging skill provides a structured, evidence-based approach to identify root causes of bugs before applying fixes, reducing guesswork and wasted effort.

Core Features & Use Cases

Phase-driven investigation guides users through Understanding, Reproduction, Isolation, Fix, and Verify.
Rigorous journaling and falsifiable hypotheses ensure transparent, repeatable debugging and easier collaboration.
Escalation and verification rules prevent premature shipping and help with complex, multi-component systems.

Quick Start

Create the debug journal and begin Phase 1 by documenting symptoms and reproduction steps.

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I find the root cause of a bug before applying fixes?▼

Root-cause debugging identifies and proves the underlying cause of a bug through a structured five-phase workflow: Understanding, Reproduction, Isolation, Fix, and Verify. This systematic investigation reduces guesswork by enforcing evidence-based isolation and falsifiable hypotheses.

How do I systematically reproduce an isolated bug across codebases and test environments?▼

Systematic reproduction requires documenting symptoms and following structured isolation rules across codebases and environments. A rigorous debug journal tracks reproduction steps, ensuring the bug is consistently repeatable before moving to the fix phase.

What is falsifiable hypothesis testing in software debugging?▼

Falsifiable hypotheses in debugging are proposed root causes that can be explicitly proven or disproven through testing. This approach enforces transparent, repeatable investigation by documenting each test and result in a debug journal before applying incremental fixes.

What's the best way to debug complex multi-component systems without premature shipping?▼

Debugging complex multi-component systems requires explicit verification steps and escalation rules to prevent premature shipping. The structured workflow enforces incremental fixes and verification across all affected components before resolution is confirmed.

Why do I need a debug journal for my testing and investigation workflow?▼

A debug journal ensures transparent, repeatable debugging and easier collaboration by documenting symptoms, reproduction steps, and falsifiable hypotheses. It provides an evidence-based record of the investigation across phases, preventing wasted effort and guesswork.