diagnosing-bugs

Diagnose uncertain bug and performance regression root causes into a structured Diagnosis Packet.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/duchuyn04/resume-analyze --skill diagnosing-bugs-duchuyn04
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/duchuyn04/resume-analyze/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/duchuyn04/resume-analyze --skill diagnosing-bugs-duchuyn04

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When a bug, regression, or performance issue has no evidence-backed root cause, teams often jump straight to fixes based on guesses. This Skill enforces a disciplined, read-only diagnostic workflow that reproduces the exact reported symptom, tests falsifiable hypotheses, and returns a structured Diagnosis Packet before any code change is proposed. ## Core Features & Use Cases - Red-Capable Feedback Loops: Builds a deterministic reproduction loop (existing test, HTTP/CLI exercise, browser scenario, or throwaway harness) that asserts the exact user-reported symptom. - Hypothesis Testing: Generates 3-5 ranked, falsifiable hypotheses and confirms root cause only when a probe distinguishes it from alternatives. - Structured Diagnosis Packet: Returns status, symptom, evidence, root cause, affected symbols, regression seam, and remaining uncertainty in a fixed schema. - Use Case: A user reports intermittent checkout failures. Use this Skill to reproduce the failure at a measured rate, isolate the load-bearing inputs, confirm the failing code path, and hand off a regression seam for the fix. ## Quick Start Ask the agent to diagnose why the reported bug happens and return a Diagnosis Packet 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 diagnose a bug with an unknown root cause?▼

Build a feedback loop that reproduces the exact reported symptom, minimize the inputs until every element is load-bearing, then test 3-5 ranked falsifiable hypotheses one variable at a time. Confirm the root cause only when a probe distinguishes it from alternatives.

How to reproduce intermittent or nondeterministic bugs?▼

Run the reproduction loop repeatedly to measure and raise the reproduction rate, recording the observed frequency. A nearby or occasional failure is not evidence for the reported bug; the loop must assert the exact reported symptom.

When should I not use a diagnostic workflow for bugs?▼

Skip structured diagnosis when the root cause and supporting evidence are already clear; in that case a normal fix proposal can be prepared directly. Diagnosis is only for uncertain root causes.

Can diagnosis modify source code or tests before approval?▼

No. Before approval, work is read-only: you may run existing tests, applications, and debuggers, and create throwaway harnesses outside permanent source. Permanent source, tests, configuration, and migrations must not be modified.

What is a regression seam in bug diagnosis?▼

A regression seam is the interface where a post-approval regression test can observe the real failure pattern. If no correct seam exists, that architecture limitation is recorded rather than adding a shallow test that cannot fail for the reported bug.