Overview

Debug Helper provides a repeatable framework for identifying and fixing software bugs. It guides you through reproducing issues, isolating the problem, forming and testing hypotheses, applying fixes, and verifying results.

How This Skill Works

The approach follows a structured investigation: reproduce the issue, isolate the affected area, and formulate a testable hypothesis. You then test the hypothesis, apply the fix, and verify the solution, using logging, breakpoints, boundary checks, and comparison of current versus working states to pinpoint root causes.

When to Use It

• Reproducing a new bug report consistently to establish a baseline
• Diagnosing a regression after a code change
• Debugging intermittent issues with a clear hypothesis testing loop
• Verifying that a fix resolves the root cause and doesn’t introduce new issues
• Onboarding teammates to a systematic debugging workflow

Quick Start

1. Step 1: Reproduce the issue consistently to establish a baseline.
2. Step 2: Isolate the problem area, add targeted logging or breakpoints, and collect evidence.
3. Step 3: Form a hypothesis, test it, implement the fix, and verify the solution.

Best Practices

• Reproduce issues deterministically before making changes
• Isolate the smallest problematic area to reduce scope
• Form testable hypotheses and design experiments to falsify them
• Instrument with targeted logging, breakpoints, and boundary checks
• Review recent changes and compare failing vs passing states to identify root cause

Example Use Cases

• Debugging a null reference that surfaced after a recent merge by tracing input flow and adding boundary checks
• Tracing a stack trace to locate the root cause of a failing API call through selective logging
• Identifying an off-by-one error by reviewing loop boundaries and validating edge cases
• Investigating a regression after a commit by comparing production vs staging state
• Reproducing a flaky UI behavior with step-through debugging and instrumentation

Frequently Asked Questions