diagnose

Run a six-phase debugging loop from reproduction to regression testing.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill diagnose-remiconnesson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/remiconnesson/nuxt-minimal-starter-v0-template/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill diagnose-remiconnesson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Diagnose skill enforces a disciplined, end-to-end debugging loop to reproduce, minimise, hypothesise, instrument, fix, and regression-test hard bugs.

Core Features & Use Cases

  • Systematic phases: reproduce, minimise, hypothesise, instrument, fix, and regression-test to guide bug resolution.
  • Works across codebases and environments by providing a repeatable process, artefacts, and decision criteria.
  • Use Case: when a user reports a hard bug or performance regression, apply this skill to steer the debugging effort and close the loop.

Quick Start

Start a reproducible bug loop on the failing scenario and begin hypothesising.

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 that are difficult to reproduce?

Debugging hard bugs requires a structured six-phase workflow enforcing a disciplined loop from reproduction to regression testing. It guides hypothesis formation and instrumentation across codebases and CI pipelines to systematically close the loop.

What is the best way to investigate a performance regression in a CI pipeline?

Investigating a performance regression involves an iterative debugging loop starting with reproduction and minimisation. It provides explicit progression criteria and artefacts to guide your diagnosis across development environments.

How do I structure a bug triage process for crash investigations?

Structuring a bug triage process for crash investigations uses systematic phases: reproduce, minimise, hypothesise, instrument, fix, and regression-test. This enforces decision criteria and artefact generation to steer the resolution effort.

Does this structured debugging workflow work across different development environments?

This structured debugging workflow works across codebases, CI pipelines, and development environments. It provides a repeatable process with explicit artefacts and progression criteria for bug reports, performance regressions, and crashes.

When should I use a structured hypothesis loop instead of standard debugging?

Use a structured hypothesis loop when standard debugging fails on hard bugs. It enforces disciplined progression from reproduction to regression testing, ensuring you minimise the failing scenario and instrument the codebase rather than guessing.