diagnosing-bugs

Diagnose hard bugs and performance regressions through a structured feedback-loop workflow.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/salomepoulain/makery-stations --skill diagnosing-bugs-salomepoulain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/salomepoulain/makery-stations/tree/main/stations/claude/workbench/pantry/skills/diagnosing-bugs
Command: npx skills add https://github.com/salomepoulain/makery-stations --skill diagnosing-bugs-salomepoulain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Hard bugs and performance regressions resist casual code reading; without a reproducible signal, debugging devolves into guessing. This Skill enforces a disciplined six-phase diagnosis loop that builds a tight pass/fail feedback signal first, then reproduces, minimizes, hypothesizes, instruments, fixes, and cleans up. ## Core Features & Use Cases - Feedback loop construction: Builds a red-capable, deterministic, fast reproduction command using failing tests, curl scripts, CLI fixtures, headless browser scripts, trace replay, fuzz loops, or bisection harnesses. - Structured hypothesis testing: Generates 3-5 ranked falsifiable hypotheses, then instruments with tagged debug logs or debugger breakpoints, changing one variable at a time. - Regression testing and cleanup: Writes the regression test before the fix at a correct seam, verifies the original repro no longer fails, and removes all tagged instrumentation. - Use Case: A user reports an export button throwing an error in production. The Skill drives creation of a curl-based repro loop, minimizes the failing scenario, tests ranked hypotheses, applies the fix, and leaves a regression test behind. ## Quick Start Ask the assistant to diagnose the bug where the export button throws an error, following the diagnosing-bugs workflow to build a reproduction loop first.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I debug a bug that I cannot reproduce consistently?

Non-deterministic bugs require raising the reproduction rate rather than finding a clean repro. Loop the trigger 100 times, parallelize, add stress, narrow timing windows, or inject sleeps until the failure rate is high enough to debug against.

What is a feedback loop in debugging and why build one first?

A feedback loop is a single command that goes red on the specific bug and green once fixed. Building it first prevents premature hypothesizing; bisection, instrumentation, and hypothesis testing all consume this signal to locate the cause.

How do I debug a bug that only a human can trigger in the UI?

Use the human-in-the-loop bash template in scripts/hitl-loop.template.sh. The script prompts the user through manual steps and captures their observations as structured output the agent can parse and act on.

When should I write a regression test for a bug fix?

Write the regression test before the fix, but only at a correct seam where the test exercises the real bug pattern as it occurs at the call site. If no correct seam exists, document that architectural finding instead of writing a shallow test.

How do I debug a performance regression differently from a functional bug?

Performance regressions need measurement rather than logs. Establish a baseline with a timing harness, profiler, or query plan, then bisect against that baseline; measure first and fix second.