diagnosing-bugs

Diagnose bugs and performance regressions using reproducible test loops.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill diagnosing-bugs-ian-pascoe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill diagnosing-bugs-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you diagnose hard bugs and performance regressions by turning vague failures into a repeatable, testable reproduction loop.

Core Features & Use Cases

  • Build a red-capable loop: Create a failing test, curl script, CLI repro, browser script, or harness that catches the exact symptom.
  • Minimize and prove: Shrink the scenario to the smallest case that still fails, then use targeted instrumentation to test ranked hypotheses.
  • Fix with confidence: Convert the minimized repro into a regression test, apply the fix, and verify the original issue is gone.
  • Use case: A service is intermittently slow, a UI action fails only in production, or a recent change introduced a subtle breakage that needs a disciplined debug plan.

Quick Start

Use the diagnosing-bugs skill to build a tight reproduction loop for the failure, run it until it goes red, and then minimize the case before testing hypotheses.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I debug flaky behavior and intermittent performance regressions in a service?

Build a red-capable reproduction loop using a failing test, curl script, CLI repro, or browser script that catches the exact symptom. Run this harness until it consistently fails before minimizing the scenario and testing ranked hypotheses.

What is the best way to turn a vague production failure into a regression test?

Reproduce the vague failure with a tight feedback loop, shrink the scenario to the smallest failing case, apply the fix, and convert the minimized reproduction into a regression test to verify the original issue is resolved.

Can I use bisection and instrumentation to diagnose unclear defects across tests and UI flows?

Yes, this approach applies to hard failures, flaky behavior, and unclear defects across tests, services, CLIs, and UI flows by requiring a tight red-capable feedback loop, reproducible evidence, ranked falsifiable hypotheses, and targeted instrumentation.

How do I minimize a bug reproduction scenario to isolate the root cause?

Shrink the failing scenario to the smallest case that still reproduces the defect, then use targeted instrumentation to test ranked falsifiable hypotheses against that minimized reproduction loop to isolate the root cause.

Why does my disciplined debug plan fail to catch subtle breakages introduced by recent changes?

A debug plan fails when it lacks a tight red-capable feedback loop and reproducible evidence. Diagnosing subtle breakages from recent changes requires ranked falsifiable hypotheses, targeted instrumentation, and regression testing to verify the fix.