diagnosing-bugs

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

3|1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/DuckKota/my-opencode-setup --skill diagnosing-bugs-duckkota
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/DuckKota/my-opencode-setup/tree/main/src/skills/diagnosing-bugs
Command: npx skills add https://github.com/DuckKota/my-opencode-setup --skill diagnosing-bugs-duckkota

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Hard bugs and performance regressions resist casual code reading; without a reproducible signal, debugging devolves into guessing. This Skill enforces a disciplined diagnosis loop that builds a tight pass/fail feedback signal first, then reproduces, minimizes, hypothesizes, instruments, fixes, and cleans up. ## Core Features & Use Cases - Feedback Loop Construction: Builds a red-capable, deterministic, fast repro command using failing tests, curl scripts, headless browser runs, trace replays, fuzz loops, or bisection harnesses. - Structured Hypothesis Testing: Generates 3-5 ranked falsifiable hypotheses, then instruments with tagged debug logs or profilers, changing one variable at a time. - Regression Lockdown: Writes a regression test at a correct seam before the fix, verifies the original repro, and removes all debug instrumentation during cleanup. - Use Case: A user reports an intermittent export failure in production. The Skill drives creation of a replay harness from a captured request, minimizes the failing scenario, tests ranked hypotheses, and lands a fix with a regression test. ## Quick Start Ask the agent to diagnose the bug where the export button throws an error, and have it build a reproduction loop before proposing any fix.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
What cleanup is required after fixing a diagnosed bug?▼

Re-run the original feedback loop to confirm the fix, verify the regression test passes, grep and remove all tagged [DEBUG-...] logs, delete throwaway prototypes, and record the correct hypothesis in the commit message.