diagnosing-bugs

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

28|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/NauelG/astro-blocks --skill diagnosing-bugs-nauelg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/NauelG/astro-blocks/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/NauelG/astro-blocks --skill diagnosing-bugs-nauelg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Hard bugs and flaky performance regressions resist casual code reading; this Skill enforces a disciplined six-phase diagnosis loop so you build a reproducible failing signal before forming hypotheses, instead of guessing at fixes. ## Core Features & Use Cases - Feedback-loop construction: Build a tight, deterministic, red-capable command (failing test, curl script, headless browser, replayed trace, bisection harness) that goes red on the exact bug before any hypothesis work. - Structured hypothesis testing: Generate 3-5 ranked falsifiable hypotheses, instrument with tagged debug logs, and change one variable at a time. - Regression locking: Convert the minimised repro into a failing regression test at a correct seam, apply the fix, and clean up all instrumentation. - Use Case: A user reports the export endpoint intermittently returns empty files. Use this Skill to build a loop that replays the failing request 100 times, minimise the repro, bisect hypotheses, and land a fix with a regression test. ## Quick Start Diagnose this bug: the checkout page throws a 500 error when the cart contains more than three items.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
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 itself.