diagnosing-bugs

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

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill diagnosing-bugs-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill diagnosing-bugs-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Hard bugs and flaky performance regressions resist casual code reading; without a reproducible pass/fail signal, debugging devolves into guessing. This Skill enforces a disciplined six-phase diagnosis loop that builds a tight, deterministic reproduction before any hypothesis is tested. ## 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. - Ranked Hypothesis Testing: Generates 3-5 falsifiable hypotheses, then instruments with tagged debug logs or debugger breakpoints, changing one variable at a time. - Regression Test & Cleanup Discipline: Writes the regression test before the fix at a correct seam, then removes all tagged instrumentation and throwaway prototypes. - Use Case: A user reports that an export endpoint intermittently throws a 500 error. The Skill guides building a curl-based loop that reproduces the failure, minimizing the repro, testing ranked hypotheses, and landing a fix with a regression test. ## Quick Start Ask the agent to diagnose the bug where the export button intermittently fails, and have it build a reproduction loop before proposing any fix.

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 only happens sometimes?▼

For non-deterministic bugs, raise the reproduction rate instead of seeking a clean repro: loop the trigger 100 times, parallelize, add stress, and narrow timing windows. A 50%-flake bug is debuggable; keep increasing the rate until it is.

What is a feedback loop in debugging?▼

A feedback loop is a single command, such as a failing test, curl script, or headless browser script, that goes red on the specific bug and green once fixed. It must be deterministic, fast, and runnable unattended before any hypothesis work begins.

How do I diagnose a performance regression?▼

For performance regressions, establish a baseline measurement first using a timing harness, performance.now(), a profiler, or a query plan, then bisect between known states. Logs are usually the wrong tool; measure first, fix second.

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.

What if I cannot reproduce the bug at all?▼

Stop and say so explicitly, listing what you tried. Ask the user for environment access, a redacted captured artifact such as a HAR file or log dump, or permission to add temporary production instrumentation rather than hypothesizing without a loop.