debug

Guide hypothesis-driven debugging through structured investigation and evidence collection.

16|3|Updated Feb 7, 2026

Search Tags:#debugging #investigation #frontend #backend #playwright #reproduction #hypotheses

Ready to run

npx skills add https://github.com/Ratler/dream-team --skill debug-ratler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Ratler/dream-team/tree/main/skills/debug
Command: npx skills add https://github.com/Ratler/dream-team --skill debug-ratler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through debugging by encouraging systematic investigation, hypothesis formation, and evidence-based resolution.

Core Features & Use Cases

Hypothesis-driven debugging: generate and test 2-3 theories about root causes with clear test steps.
Structured investigation: read relevant context, reproduce the issue, and collect evidence.
Interactive guidance: ask one precise question at a time and iteratively converge on a fix.

Quick Start

Describe the issue, reproduce it, and guide me through hypothesis-driven investigation.

Frequently Asked Questions about debug

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

FAQPage Schema

What is hypothesis-driven debugging and how does it work?▼

Hypothesis-driven debugging is an investigation method that narrows down 2-3 plausible root causes and validates each theory with concrete test steps to find and resolve the issue.

How do I debug a frontend issue using a structured investigation process?▼

To debug a frontend issue, you start by reproducing it and gathering evidence, then generate 2-3 hypotheses about the root causes and iteratively validate each theory with clear, concrete steps.

Can I use this approach to debug backend and Playwright reproduction failures?▼

Yes, this approach applies to backend and Playwright reproduction failures by structuring the investigation, asking precise clarifying questions, and validating root cause hypotheses with evidence.

What's the best way to find a root cause when I can't reproduce the bug?▼

The best way to find a root cause when you cannot reproduce the bug is to gather contextual evidence through clarifying questions, form 2-3 plausible hypotheses, and test each theory systematically.

How do I create a clear plan to verify my debugging fix?▼

To create a verification plan for your debugging fix, validate each root cause hypothesis with concrete reproduction steps, then confirm the proposed resolution resolves the original issue.