diagnosing-bugs

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

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/MaksymilianCzadowski/skills --skill diagnosing-bugs-maksymilianczadowski
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/MaksymilianCzadowski/skills/tree/main/skills/engineering/diagnosing-bugs
Command: npx skills add https://github.com/MaksymilianCzadowski/skills --skill diagnosing-bugs-maksymilianczadowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hard bugs and performance regressions stall when developers jump straight to hypotheses without a reproducible signal. This Skill enforces a disciplined 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: Ten ordered strategies for building a red-capable test signal, from failing tests and curl scripts to replayed traces, fuzz loops, and git bisect harnesses. - Structured hypothesis testing: Generates 3-5 ranked, falsifiable hypotheses before testing, with one-variable-at-a-time instrumentation and tagged debug logs for clean removal. - Regression and post-mortem discipline: Writes regression tests at correct seams before fixing, verifies the original repro, removes instrumentation, and captures the root cause in the commit message. - Use Case: A user reports their API endpoint intermittently returns wrong data. The Skill guides building a deterministic failing test, minimizing the repro, ranking hypotheses, instrumenting with tagged logs, and landing a fix with a regression test. ## Quick Start Ask the assistant to diagnose the bug you are experiencing and describe the exact symptom, error message, or slowdown you observed.

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, and inject sleeps until the failure rate is high enough to debug against.

How to diagnose a performance regression in code?▼

Performance regressions need measurement before fixing. Establish a baseline with a timing harness, performance.now(), a profiler, or query plans, then bisect between known-good and known-bad states to isolate the cause.

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

A feedback loop is a single command, such as a test, curl script, or CLI invocation, that goes red on the specific bug and green once fixed. Building it first ensures bisection, hypothesis testing, and instrumentation all consume a reliable signal instead of guesswork.

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 gap as a finding instead of writing a shallow test.

What should I do if I cannot build any reproduction for a bug?▼

Stop and say so explicitly rather than hypothesizing without a signal. Ask the user for environment access, a captured artifact like a HAR file or log dump, or permission to add temporary production instrumentation.