diagnose

Diagnose hard bugs through reproduction, minimization, and instrumentation.

Updated May 2, 2026
One-click install
npx skills add https://github.com/maxenergy/skills --skill diagnose-maxenergy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/maxenergy/skills/tree/main/skills/engineering/diagnose
Command: npx skills add https://github.com/maxenergy/skills --skill diagnose-maxenergy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a structured interrogation of hard bugs, guiding you from initial reproduction to a minimal, well-supported fix through a repeatable diagnostic loop.

Core Features & Use Cases

  • Reproduce efficiently: Rapidly reproduce issues with deterministic steps and signals.
  • Minimise and hypothesise: Reduce the reproduction case and form testable hypotheses about the root cause.
  • Instrument and verify: Add instrumentation, collect signals, and confirm regressions are resolved across scenarios.

Quick Start

Describe a bug you want diagnosed and let the skill guide you through reproduction, minimisation, hypothesis testing, instrumentation, and regression testing.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug a hard bug that is difficult to reproduce?

To debug a hard bug, you need a disciplined diagnostic loop that establishes a deterministic feedback loop to reproduce the issue, minimises the reproduction case, and forms testable hypotheses about the root cause using collected signals.

What is the best way to diagnose a performance regression in my codebase?

Diagnosing a performance regression requires instrumenting tests to collect signals, reducing the reproduction case to a minimal example, and verifying the regression is resolved across scenarios using evidence-driven debugging.

How do I create a minimal reproduction case for a complex regression?

Creating a minimal reproduction case involves systematically reducing the steps and conditions that trigger the regression while maintaining a deterministic feedback loop to confirm the issue persists until you isolate the root cause.

Do I need instrumented tests to use a structured debugging loop?

Yes, instrumented tests are required for a structured debugging loop because they provide the deterministic feedback loop and collected signals necessary to form testable hypotheses and validate fixes against regressions.

How does hypothesis-driven debugging work when fixing bugs?

Hypothesis-driven debugging works by forming testable assumptions about the root cause, adding instrumentation to collect signals, and verifying or disproving each hypothesis against evidence gathered from a minimised reproduction case.

Can I guard against future regressions after applying a bug fix?

Yes, you can guard against future regressions by establishing a clear end-to-end plan that uses instrumented tests to validate fixes and confirm the original regression is resolved across all relevant scenarios.