diagnose

Diagnose bugs and performance regressions with a structured 6-phase workflow.

4|Updated May 20, 2026
One-click install
npx skills add https://github.com/valorisa/Claude-Skills --skill diagnose-valorisa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/valorisa/Claude-Skills/tree/main/skills/diagnose
Command: npx skills add https://github.com/valorisa/Claude-Skills --skill diagnose-valorisa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the guesswork and wasted effort of unstructured debugging, helping developers systematically identify root causes of hard bugs and performance regressions instead of wasting time on random shotgun fixes that fail to resolve underlying issues.

Core Features & Use Cases

  • Structured 6-phase debugging workflow: Guides users through reproduce, minimise, hypothesise, instrument, fix, and regression test steps to ensure bugs are fully resolved and won't recur.
  • Feedback loop construction guidance: Provides 10 ranked methods to build fast, deterministic reproduction loops even for non-deterministic or hard-to-reproduce bugs.
  • Use Case: If your team is dealing with an intermittent test failure that only occurs 10% of the time, or a performance regression that appeared after a recent deploy, this Skill guides you through building a reliable repro, testing ranked falsifiable hypotheses, and implementing a fix with a proper regression test.

Quick Start

Use the diagnose skill to systematically debug the reported bug or performance regression in your codebase by following the structured 6-phase workflow.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is the best way to debug intermittent test failures and performance regressions?

Systematic debugging eliminates guesswork for intermittent test failures and performance regressions by applying a structured 6-phase workflow to deterministically identify root causes instead of attempting random fixes.

How do I build a reliable reproduction loop for non-deterministic bugs?

To build a reliable reproduction loop for non-deterministic bugs, use feedback loop construction guidance that provides 10 ranked methods to create fast, deterministic reproduction steps for hard-to-reproduce issues.

How do you perform root cause analysis for a post-deployment performance regression?

Root cause analysis for a post-deployment performance regression requires reproducing the issue, minimizing variables, testing falsifiable hypotheses, instrumenting the code, fixing, and running regression tests to ensure permanent resolution.

Does this debugging workflow work for intermittent issues that only occur rarely?

Yes, this debugging workflow is designed for intermittent issues occurring rarely, using feedback loop construction and ranked falsifiable hypothesis testing to build reliable reproduction scenarios for hard bugs.

What are the limitations of unstructured debugging for hard bugs?

Unstructured debugging for hard bugs causes wasted developer time and shotgun fixes that fail to resolve underlying issues, lacking the disciplined hypothesis testing needed for permanent resolution of complex regressions.