autoresearch:debug

Guide bug hunting through falsifiable hypotheses and structured investigation loops.

29|4|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/wjgoarxiv/autoresearch-skill --skill autoresearch-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresearch:debug
Source: https://github.com/wjgoarxiv/autoresearch-skill/tree/main/skills/debug
Command: npx skills add https://github.com/wjgoarxiv/autoresearch-skill --skill autoresearch-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to bug hunting using falsifiable hypotheses, helping users to scientifically investigate and resolve bugs in a structured manner.

Core Features & Use Cases

  • Hypothesis Formation: Guides users in formulating falsifiable hypotheses for troubleshooting.
  • Investigation Loop: Orchestrates the scientific method in the form of an investigation loop, including observing, hypothesizing, designing tests, running tests, updating hypothesis sets, and logging.
  • Output Structure: Delivers a structured debug/ directory with files for active hypotheses, eliminated hypotheses, and findings.
  • Use Case: For users encountering a bug and needing a systematic approach to identify the root cause.

Quick Start

To start a bug investigation, run the command: /autoresearch:debug.

Frequently Asked Questions about autoresearch:debug

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

FAQPage Schema
What is systematic debugging with falsifiable hypotheses?

Systematic debugging with falsifiable hypotheses is a scientific method for bug hunting that structures investigations into a loop: observing, hypothesizing, designing tests, running tests, and updating active hypothesis sets to isolate root causes.

How do I find a root cause using a structured investigation loop?

To find a root cause, form falsifiable hypotheses, design specific tests to challenge them, run the tests, and update your hypothesis sets. This Skill orchestrates the investigation loop and logs active and eliminated hypotheses in a structured debug directory.

Do I need Python and command-line tools for scientific bug hunting?

Yes, scientific bug hunting using this Skill requires Python for scripting and various command-line tools to design tests, run investigations, and validate falsifiable hypotheses during the debugging process.

What's the best way to track eliminated hypotheses during bug hunting?

The best way to track eliminated hypotheses is to use a structured output directory. This Skill automatically generates a debug folder with files specifically logging active hypotheses, eliminated hypotheses, and findings.

Are there limitations to using a scientific debugging approach for troubleshooting?

A limitation of scientific debugging is that it requires Python and command-line tool proficiency. Users must methodically form and test falsifiable hypotheses rather than relying on ad-hoc inspection to resolve complex bugs.