diagnosing-bugs

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

1|Updated Apr 25, 2025
One-click install
npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill diagnosing-bugs-gabr1elaugus700
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/Gabr1elaugus700/WorkaPool/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/Gabr1elaugus700/WorkaPool --skill diagnosing-bugs-gabr1elaugus700

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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 ranked strategies for building a red-capable repro, from failing tests and curl scripts to headless browser runs, trace replay, fuzz loops, and git bisect harnesses. - Structured hypothesis testing: Generates 3-5 ranked, falsifiable hypotheses and maps each instrumentation probe to a specific prediction, changing one variable at a time. - Regression test discipline: Writes the regression test before the fix at a correct seam, then verifies with the original repro and removes all tagged debug instrumentation. - Use Case: A user reports that the export button intermittently throws an error. The Skill guides building a deterministic repro script, minimizing the failing scenario, testing ranked hypotheses, and landing a fix with a regression test. ## Quick Start Ask the agent to diagnose the bug where the export button throws an error and have it build a reproducible failing test 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 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.

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 states. Logs are usually the wrong tool for perf work.

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, hypothesis testing, and instrumentation all consume this signal.

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 as an architectural finding.

What if I cannot build any reproduction for a reported bug?

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