diagnosing-bugs

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

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill diagnosing-bugs-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill diagnosing-bugs-tanqimin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Hard bugs and performance regressions resist casual debugging: staring at code rarely finds the cause. This Skill enforces a disciplined six-phase diagnosis loop that builds a tight, red-capable feedback signal first, then reproduces, minimises, hypothesises, instruments, fixes, and cleans up. ## Core Features & Use Cases - Feedback loop construction: Ten ranked strategies for building a pass/fail signal, from failing tests and curl scripts to replayed traces, fuzz loops, bisection harnesses, and human-in-the-loop bash scripts. - Structured hypothesis testing: Generates 3-5 ranked, falsifiable hypotheses before testing, then instruments one variable at a time with tagged debug logs for easy cleanup. - Regression locking: Turns the minimised repro into a failing regression test at a correct seam before applying the fix, with a mandatory cleanup checklist. - Use Case: A user reports an intermittent production error. The Skill guides building a high-reproduction-rate loop, minimising the failing scenario, ranking hypotheses, and landing a fix with a regression test. ## Quick Start Ask the assistant to diagnose the bug where the export button throws an intermittent error, following the phased diagnosis loop.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I debug an intermittent or flaky bug?

Raise the reproduction rate instead of chasing a clean repro: loop the trigger 100 times, parallelise, add stress, narrow timing windows, or inject sleeps. A 50%-flake bug is debuggable; keep increasing the rate until your feedback loop reliably goes red.

How to diagnose a performance regression in code?

Establish a baseline measurement first using a timing harness, profiler, or query plan, then bisect to find the regression point. Logs are usually the wrong tool for performance work; measure first and fix second.

What should I do when I cannot reproduce a bug?

Stop and say so explicitly rather than hypothesising without a signal. 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.

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

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

Why does debugging without a failing test often fail?

Without a tight pass/fail signal that goes red on the specific bug, hypothesis-testing and instrumentation have nothing to consume. Building a fast, deterministic, red-capable loop first is what makes the cause findable.