diagnosing-bugs

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

1|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/taxmaxi/taxmaxi --skill diagnosing-bugs-taxmaxi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/taxmaxi/taxmaxi/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/taxmaxi/taxmaxi --skill diagnosing-bugs-taxmaxi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Hard bugs and flaky performance regressions resist ad-hoc debugging: staring at code rarely finds the cause. This Skill enforces a disciplined six-phase diagnosis loop that builds a tight, deterministic pass/fail signal first, then reproduces, minimises, hypothesises, instruments, fixes, and cleans up. ## Core Features & Use Cases - Feedback-loop construction: Ten ranked strategies for building a red-capable reproduction command, from failing tests and curl scripts to bisection harnesses, differential loops, and human-in-the-loop bash scripts. - Structured hypothesis testing: Generates 3-5 ranked, falsifiable hypotheses before testing, then instruments with tagged debug logs or profiler baselines, changing one variable at a time. - Regression lockdown and cleanup: Writes the regression test before the fix at a correct seam, then verifies the original repro, removes all tagged instrumentation, and records the confirmed root cause. - Use Case: A user reports that an export endpoint intermittently returns stale data. The Skill guides building a deterministic failing test, minimising the repro, ranking hypotheses, instrumenting the suspected cache layer, and landing a fix with a regression test. ## Quick Start Ask the agent to diagnose the bug where the export endpoint intermittently returns stale data and have it build a failing 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 only happens intermittently?▼

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

How to create a reproduction script for a hard bug?▼

Build a feedback loop at whatever seam reaches the bug: a failing test, a curl script against a dev server, a CLI invocation with fixture input, a headless browser script, or a replayed captured trace. The loop must assert the user's exact symptom and run deterministically in seconds.

What is the best way to debug performance regressions?▼

For performance regressions, establish a baseline measurement first using a timing harness, performance.now(), a profiler, or query plans, then bisect between known states. Logging is usually the wrong tool for perf work; 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 instead of writing a shallow test that gives false confidence.

Why does debugging without a reproduction loop fail?▼

Without a tight pass/fail signal that goes red on the specific bug, hypothesis testing and instrumentation have nothing to consume, and fixes cannot be verified. The workflow refuses to proceed to hypothesising until a red-capable, deterministic, fast command exists.