hermeticormus/hypothesis-debugging-skills · Archived
Hypothesis-driven debugging protocol — reproduce, isolate, hypothesize, test, fix, document.
npx skills add hermeticormus/hypothesis-debugging-skills --skill hypothesis-debugging
This repository is archived — consider an actively maintained alternative.
Frame an epic as a testable hypothesis with target user, expected outcome, and validation metho…
2K installsGenerate falsifiable trade strategy hypotheses from market data, trade logs, and journal snippe…
1.8K installsFormulate evidence-bounded scientific questions, candidate hypotheses, rival explanations, caus…
1.5K installsDefines a testable hypothesis with clear success metrics and a validation approach.
687 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Day 2 end capstone move of a Foundation Sprint.
521 installsConduct statistical tests including t-tests, chi-square, ANOVA, and p-value analysis for statis…
474 installsDeclared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
2,348 B
SUMMARY.md
378 B
A six-phase protocol for debugging. Do not write a fix until you have a ranked hypothesis table and a confirmed root cause.
Tradeoff: bias toward finding the cause over shipping a fast patch. For an obvious one-line typo, use judgment.
Make the failure happen on demand. Capture the exact error and stack trace, the repro steps, and expected versus actual. Consistent or intermittent? Intermittent points at state, timing, or environment.
Narrow the scope. Check recent commits (git log --oneline -10) and diffs, then reduce to the smallest input that still fails.
Write a ranked hypothesis table BEFORE touching the code.
| # | Hypothesis | Likelihood | How to test |
|---|---|---|---|
| 1 | Most likely cause, stated specifically | High | A cheap yes/no test |
| 2 | Second possibility | Medium | A specific test |
| 3 | Less likely cause | Low | A specific test |
Each row names a concrete cause and has a test that can run.
Work the table top to bottom. Confirm or refute each row. A confirmed hypothesis is the root cause; a refuted one is removed. Do not skip to a fix on a hunch.
With the cause confirmed: the smallest change that addresses it, traced for side effects, verified against the Phase 1 reproduction, plus a regression test that fails on the old code.
Root cause, not workaround. Reject try/catch swallowing, defensive masking checks, renamed symptom variables, mocked broken dependencies, and asserting the bug away. A workaround that passes tests hides the bug and propagates it.
Record the root cause, the fix and why it addresses the cause, and the prevention: the regression test, the bug category, and how to catch this class faster next time.
See full content and worked examples at https://github.com/HermeticOrmus/hypothesis-debugging-skills.