skills.rest
miptah21
miptah21COMMUNITY
Explore all skills by this author →
GitHub

diagnose

Diagnose bugs and performance regressions through an evidence-based debugging loop.

2|Updated Apr 8, 2026
Search Tags:#debugging#hypothesis testing#instrumentation#regression testing#performance regression#trace replay#test-driven diagnosis
One-click install
npx skills add https://github.com/miptah21/skills --skill diagnose-miptah21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/miptah21/skills/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/miptah21/skills --skill diagnose-miptah21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you systematically diagnose hard bugs and performance regressions instead of guessing, so you can reliably reach the root cause.

Core Features & Use Cases

  • Feedback-loop first diagnosis: builds a fast, deterministic pass/fail signal and iterates on it until the bug is debuggable.
  • Reproduce → hypothesize → instrument → fix: runs the structured phases to narrow causes using falsifiable predictions and targeted probes.
  • Regression safety: turns the minimized repro into a failing regression test (when a correct seam exists) to prevent backsliding.

Quick Start

Run the diagnose loop for the failing bug by first constructing a deterministic repro signal (test, HTTP script, CLI fixture, trace replay, or harness) and then iterating through reproduce, ranked falsifiable hypotheses, targeted instrumentation, and a verified fix with cleanup.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug hard bugs without guessing at the root cause?▼

Debugging performance regressions requires building a fast, deterministic pass/fail signal using a test, HTTP script, CLI fixture, or trace replay, then iterating through structured phases to narrow causes with targeted probes.

What is the best way to reproduce a failing behavior for diagnosis?▼

Reproduce a failing behavior by constructing a deterministic repro signal such as a test, HTTP script, CLI fixture, or trace replay harness, ensuring the bug can be consistently triggered before hypothesizing causes.

How does hypothesis testing work when diagnosing software bugs?▼

Hypothesis testing during bug diagnosis involves ranking falsifiable predictions about the failure cause, then applying targeted instrumentation tied to those predictions to validate or eliminate each hypothesis systematically.

Can I turn a minimized bug reproduction into a regression test?▼

You can turn a minimized reproduction into a failing regression test when a correct test seam exists, preventing backsliding after the fix; otherwise, the lack of test seams must be documented.

What should I do when my bug lacks test seams for regression testing?▼

When a bug lacks test seams for regression testing, you must document the lack of test seams in the diagnostic workflow, completing the loop by verifying the fix and cleaning up instrumentation without a failing test.

Related Skills

Explore More Software Engineering Skills→
janpeterdjanpeterd

diagnose

Diagnose bugs and performance regressions using deterministic pass/fail feedback loops.

Community
Advanced
romiluz13romiluz13
11

diagnosing-bugs

Diagnose software bugs through reproducible feedback loops and falsifiable hypotheses.

Community
Advanced
TrebuchetDynamicsTrebuchetDynamics
5

diagnose

Diagnose hard bugs and performance regressions through an evidence-driven feedback loop.

Official
Advanced
yuridefrancayuridefranca

root-cause-analyzer

Reproduce bugs and trace state flows to produce evidence-backed root cause reports.

Community
Advanced