diagnose

Diagnose hard bugs through a six-phase reproduction-to-regression-check loop.

2|1|Updated Oct 8, 2009
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill diagnose-riethmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/diagnose
Command: npx skills add https://github.com/riethmayer/dotfiles --skill diagnose-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Disciplined diagnosis loop for hard bugs. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Core Features & Use Cases

  • A deterministic, six-phase workflow that guides reproduction, hypothesis generation, instrumentation, and verification.
  • Detailed guidance for constructing test loops and prioritizing hypotheses.
  • A structured decision framework to decide when to escalate or stop the diagnostic process.

Quick Start

Run the six-phase loop: reproduce the bug, minimise the repro, hypothesise, instrument, fix, then regression-test.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a disciplined workflow to diagnose hard bugs that are difficult to reproduce?

A disciplined debugging loop provides a six-phase workflow: reproduce, minimise, hypothesise, instrument, fix, and regression-test to systematically resolve hard bugs and performance regressions.

How do I systematically debug a performance regression using hypothesis testing?

Systematic debugging of a performance regression requires generating explicit hypotheses, prioritising them, and adding targeted instrumentation to verify root causes before applying a fix and running regression checks.

What's the best way to minimise a bug reproduction case before fixing it?

The best way to minimise a bug reproduction is to systematically strip away irrelevant variables while confirming the bug persists, creating a deterministic test loop before forming hypotheses and instrumenting the code.

When should I escalate or stop the diagnostic process for a failing system?

You should escalate or stop the diagnostic process when a structured decision framework evaluates your instrumentation results and hypothesis outcomes, indicating that further debugging within the current loop is unproductive.

Does this debugging approach require any specific testing frameworks or dependencies?

No specific testing frameworks or dependencies are required. The diagnostic loop is a methodology applied through scripts, guiding you to construct test loops, instrument code, and verify fixes via regression-testing.