diagnose

Guide users through reproduce, minimize, hypothesize, instrument, fix, and regression-test phases.

Updated May 16, 2026
One-click install
npx skills add https://github.com/ckyeon/claude-code-settings --skill diagnose-ckyeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/ckyeon/claude-code-settings/tree/main/user/shared/skills/diagnose
Command: npx skills add https://github.com/ckyeon/claude-code-settings --skill diagnose-ckyeon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic approach to diagnose bugs and performance regressions, saving time and effort in identifying and resolving issues.

Core Features & Use Cases

  • Disciplined Diagnosis Loop: Follows a structured approach of reproduce, minimize, hypothesise, instrument, fix, and regression-test.
  • Feedback Loop Construction: Focuses on building a reliable and fast feedback loop for the bug to aid in debugging.
  • Reproduction and Hypothesizing: Ensures that the bug is reproducible and develops a hypothesis for its cause.
  • Instrumentation: Provides guidance on using different tools and methods to instrument the bug.
  • Fix and Regression Testing: Assists in writing regression tests and verifying the fix.

Quick Start

Use the diagnose skill to follow the disciplined diagnosis loop for your bug.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a systematic approach to diagnosing software bugs and performance regressions?

A systematic bug diagnosis approach guides you through structured phases: reproduction, minimization, hypothesis generation, instrumentation, fixing, and regression testing to identify and resolve issues efficiently.

How do I build a reliable feedback loop for debugging code?

To build a feedback loop for debugging, you establish a reliable and fast cycle to reproduce the bug, test hypotheses, and instrument the system, ensuring consistent verification throughout the diagnosis process.

How to minimize a reproducible bug for easier diagnosis?

To minimize a reproducible bug, you systematically strip away extraneous variables while maintaining consistent reproduction, which helps isolate the exact trigger and narrow down the root cause for hypothesis generation.

What is the best way to instrument an application when diagnosing a performance regression?

The best way to instrument for a performance regression is to apply targeted tools and methods that monitor system behavior, enabling you to measure impacts and validate your hypotheses about the slowdown.

Do I need to understand the problem domain before diagnosing a complex bug?

Yes, understanding the problem domain is required, as effective bug diagnosis depends on generating accurate hypotheses and constructing a reliable feedback loop tailored to the specific software environment.

Why write regression tests after fixing a bug?

Writing regression tests after fixing a bug ensures the specific issue remains resolved and prevents future performance regressions by verifying that the new code behaves correctly under the same conditions.