diagnosing-bugs

Diagnose bugs and performance regressions through evidence-based reproduction and verification.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill diagnosing-bugs-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/workflow/diagnosing-bugs
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill diagnosing-bugs-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Bug reports often get fixed by guesswork, leading to shallow patches that miss the real cause. This Skill enforces a disciplined reproduce → investigate → fix → verify workflow so every diagnosis is backed by evidence and every fix is verified against the original scenario. ## Core Features & Use Cases - Structured Reproduction: Establishes the exact symptom, trigger, and environment before investigating, including intermittent and performance issues with measured baselines. - Falsifiable Hypothesis Testing: Runs targeted probes that confirm or reject hypotheses one variable at a time, with tagged temporary instrumentation for clean removal. - Regression-Verified Fixes: Adds a regression test at the real failure seam, observes it fail before the fix, and reruns the original scenario to close the investigation. - Use Case: A user reports that switching projects resets their filters. The Skill guides the agent to reproduce the reset, trace the state management cause, add a failing regression test, apply the fix, and verify the original scenario end to end. ## Quick Start Diagnose why switching projects resets my filters: reproduce the issue, find the root cause with evidence, fix it, and verify the original scenario.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I diagnose a bug that is hard to reproduce?▼

Record failures per trial along with exact test conditions, since a single clean run does not prove a fix. Minimize the scenario while retaining the failure, and document the reproduction limitation explicitly if the environment cannot be matched.

How to find the root cause of a performance regression?▼

Use comparable inputs and conditions before and after the change, recording the measured quantity and baseline. Test one falsifiable hypothesis at a time with targeted instrumentation, and repeat comparable measurements after the fix.

What should a bug diagnosis report include?▼

Include the symptom and environment, the reproduction steps with expected versus observed behavior, the cause with supporting evidence, the change made, verification commands and results, and any remaining untested cases or blockers.

When should a regression test be added for a bug fix?▼

Add a regression test at the seam that exercises the actual failure once implementation is authorized. Observe it fail before the fix and pass afterward; if no suitable seam exists, report the limitation instead of writing a shallow test.

Can a bug be diagnosed without fixing the code?▼

Yes, a diagnosis-only request ends with findings and stated uncertainty and does not authorize implementation. Source inspection can narrow the cause, but it does not replace a reproduced failure as evidence.