skills.rest
dangeles
dangelesCOMMUNITY
Explore all skills by this author →
Website𝕏@sciangelesGitHub

systematic-troubleshooter

Guide phase-driven debugging from symptom capture to documented fixes.

6|Updated Feb 3, 2026
Search Tags:#workflow#debugging#documentation#root-cause-analysis#hypothesis-testing#minimal-reproducible-example
One-click install
npx skills add https://github.com/dangeles/claude --skill systematic-troubleshooter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-troubleshooter
Source: https://github.com/dangeles/claude/tree/main/claude-config/skills/systematic-troubleshooter
Command: npx skills add https://github.com/dangeles/claude --skill systematic-troubleshooter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams diagnose and resolve bugs efficiently by enforcing a structured, phase-based debugging workflow that moves from problem understanding to documented fixes.

Core Features & Use Cases

  • Phase-driven investigation: Follow a seven-phase process (Understand, Reproduce, Hypothesize, Test, Fix, Verify, Document) to isolate root causes.
  • Minimal reproducible examples: Create small, portable repros to sharpen focus and enable reliable testing.
  • Hypothesis-driven testing: Systematically test one variable at a time with formal templates to validate or dismiss theories.
  • Comprehensive documentation: Record symptoms, tests, decisions, and prevention strategies for future incidents.

Quick Start

Begin by describing observed symptoms, then draft a minimal reproduction, outline hypotheses, and execute targeted tests per the workflow.

Frequently Asked Questions about systematic-troubleshooter

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

FAQPage Schema
What is root-cause analysis for complex software bugs?▼

Root-cause analysis for complex software bugs is a disciplined, phase-driven investigation that isolates underlying causes through structured symptom capture, minimal reproducible examples, and hypothesis testing to ensure traceable fixes without regressions.

How do I debug intermittent software failures systematically?▼

Debug intermittent software failures systematically by following a seven-phase workflow: Understand, Reproduce, Hypothesize, Test, Fix, Verify, and Document, applying structured symptom capture and one-variable testing to isolate root causes.

What's the best way to troubleshoot multi-component integration failures?▼

Troubleshoot multi-component integration failures using a phase-driven investigation workflow that structures symptom capture, creates minimal repros, and systematically tests hypotheses to resolve complex software system bugs without regressions.

Does hypothesis-driven debugging work for performance degradations?▼

Hypothesis-driven debugging works for performance degradations by systematically testing one variable at a time with formal templates, guiding a structured investigation from symptom capture through minimal reproduction to verified fixes.

Why do I need documentation during root-cause analysis?▼

Documentation during root-cause analysis is needed to record observed symptoms, tested hypotheses, decisions, and prevention strategies, ensuring traceable fixes and providing reference material for future incidents.

Related Skills

Explore More Software Engineering Skills→
rafaelcostaf4-afkrafaelcostaf4-afk

debug-session

Diagnose Django bugs from symptom to root cause with regression tests.

Community
Advanced
romiluz13romiluz13
161

root-cause-analysis

Guide root cause analysis through evidence collection and hypothesis testing.

Community
Basic
SeaLion-hubSeaLion-hub

investigate

Guide structured debugging workflows to identify and resolve software issue root causes.

Community
Advanced
singhianand23045singhianand23045

gstack-openclaw-investigate

Diagnose software bugs through a structured four-phase root-cause investigation.

Community
Advanced