Individual skill

debug-hypothesis

Use when debugging any non-trivial bug — wrong output, crash, flaky test, performance regression, or "it works locally but not in CI." Forces a scientific-method loop (Observe → Hypothesize → Experiment → Conclude) so the agent stops guessing and starts reasoning. Prevents the

skills/debug-hypothesis/SKILL.md

Read pinned source

Source commit ebbc355b6db90b445649efba9a58022d049c9ee2

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 232
Repository last updated: Jun 9, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

gemini-cli-extension Repository topic
testing Derived category
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 10,307 bytes

Read excerpt


# Hypothesis-Driven Debugging

A four-phase loop that turns debugging from "try random fixes and hope" into
a disciplined investigation. Each phase has a goal, hard rules, and a
rationalization table for the excuses an agent will invent to skip it.

The core principle: **you may not write a fix until you have evidence that
your hypothesis is correct.** Guessing is not debugging.

## When to Use

- A test fails and the cause is not immediately obvious
- The same bug has been "fixed" twice and came back
- The agent tried a fix that didn't work — stop it from trying another