skills.rest
OutlineDriven
OutlineDrivenOFFICIAL
Explore all skills by this author →
GitHub

debug

Isolate root causes with a hypothesis-driven minimal-repro workflow.

5|2|Updated Nov 17, 2025
Search Tags:#debugging#breakpoints#root-cause#hypothesis-driven#trace-analysis#minimal-repro#defect-isolation
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill debug-outlinedriven
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/debug
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill debug-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A bug investigation methodology that enables deterministic defect isolation using structured hypothesis testing, stack-trace forensics, and minimal repro to confirm root cause.

Core Features & Use Cases

  • Hypothesis-driven exploration: systematically test and falsify failure causes.
  • Breakpoint and state-inspection strategy: targeted instrumentation and breakpoint workflows for fast isolation.
  • Reliable repros: construct minimal failing scenarios to validate fixes across tests, crashes, or intermittent issues.
  • Use case: when a failure's cause is unclear after a change, apply this workflow to identify the faulty assumption and verify it with a minimal repro.

Quick Start

Follow the hypothesis loop to reproduce the failure, observe traces, form hypotheses, instrument with minimum probes, run the minimal repro, and confirm the root cause.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I isolate the root cause of a crash when the defect is not obvious from the change set?▼

To isolate a root cause, apply a hypothesis-driven workflow by observing stack traces, forming failure hypotheses, instrumenting with minimal probes, and running a minimal repro to verify the faulty assumption.

What is the best way to debug intermittent faults and test failures with unclear causes?▼

Debugging intermittent faults requires constructing minimal failing scenarios to reliably reproduce the issue, then using targeted breakpoints and state inspection to deterministically confirm the root cause.

How does hypothesis-driven defect isolation work for software exceptions?▼

Hypothesis-driven defect isolation works by systematically testing and falsifying potential failure causes through structured observation, targeted instrumentation, and minimal repro execution until the root cause is proven.

Can I use breakpoint strategy and trace analysis for any type of software defect isolation?▼

Yes, breakpoint strategy and stack-trace forensics apply to test failures, crashes, exceptions, and intermittent faults, enabling fast isolation by targeting specific state inspections during minimal repro execution.

When should I use a minimal repro workflow instead of standard debugging methods?▼

Use a minimal repro workflow when a failure's cause is unclear after a change, as it enforces a structured sequence of observation and hypothesis testing to validate fixes deterministically rather than relying on guesswork.

Related Skills

Explore More Software Engineering Skills→
janjaszczakjanjaszczak

troubleshooting-rca

Identify probable root causes of software failures from logs and repro steps.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
kennyolofsson23-netizenkennyolofsson23-netizen

kaizen:root-cause-tracing

Trace errors back through call chains to locate original triggers.

Community
Advanced
nimadorostkarnimadorostkar
25

debugging

Diagnose software defects through hypothesis-driven binary-search bisection.

Community
Advanced