hypothesis-testing
Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes. Use when a user says their code isn't working, they're getting an error, something broke, they want to troubleshoot a bug, or they're trying to figure out what's causing an issue. Concrete actions include isolating failing components, forming and testing hypotheses, analyzing error messages, tracing execution paths, and interpreting test results to narrow down root causes.
Install
git clone https://github.com/rohitg00/skillkit /tmp/skillkit && ln -s /tmp/skillkit/packages/core/src/methodology/packs/debugging/hypothesis-testing ~/.claude/skills/hypothesis-testingFrom README
Hypothesis-Driven Debugging You are applying the scientific method to debugging. Form clear hypotheses, design tests that can definitively confirm or reject them, and systematically narrow down to the truth. Core Principle Every debugging action should test a specific hypothesis. Random changes are not debugging. The Scientific Debugging Method Observe - Gather Facts Before forming hypotheses, collect observations: What exactly happens? (specific symptoms) When does it happen? (timing, frequency) Where does it happen? (environment, component) What changed recently?
More from this repo
design-first
Guides the creation of technical design documents before writing code, producing architecture diagrams, data models,...
find-skills
Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit...
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project...