diagnosing-bugs

Diagnose and fix software bugs through a structured six-phase process.

Updated May 7, 2026

Search Tags:#code analysis #debugging #software development #bug diagnosis #performance regression

Ready to run

npx skills add https://github.com/Matthieusz/skills --skill diagnosing-bugs-matthieusz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/Matthieusz/skills/tree/main/diagnosing-bugs
Command: npx skills add https://github.com/Matthieusz/skills --skill diagnosing-bugs-matthieusz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a systematic approach to diagnose hard bugs and performance regressions, guiding you through a structured process to identify and fix issues efficiently.

Core Features & Use Cases

Diagnosis Loop: Offers a step-by-step guide to build a tight feedback loop for bug diagnosis.
Phase-Based Approach: Breaks down the process into six distinct phases: Build a feedback loop, Reproduce + Minimise, Hypothesise, Instrument, Fix + Regression Test, and Cleanup + Post-mortem.
Use Case: When encountering a complex bug that requires a deep dive into the codebase, this Skill helps you systematically narrow down the problem and implement a solution.

Quick Start

Use the diagnosing-bugs skill to diagnose and fix a performance regression in your application by following the structured six-phase process outlined in the SKILL.md file.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema

What is a structured approach to diagnose hard bugs in software development?▼

A structured approach to diagnose hard bugs uses a six-phase process: building a feedback loop, reproducing and minimizing, hypothesizing, instrumenting, fixing with regression tests, and cleanup with post-mortem.

How do I fix a performance regression using a systematic debugging process?▼

To fix a performance regression, follow the systematic debugging process to first reproduce and minimize the issue, form hypotheses, instrument the code for data, and then implement a fix with an automated regression test.

How do I build a tight feedback loop for bug diagnosis?▼

You build a tight feedback loop for bug diagnosis by creating a consistent reproduction case, minimizing the variables involved, and running automated tests to rapidly validate or invalidate your hypotheses.

What do I need to understand before using a systematic bug diagnosis process?▼

You need a solid understanding of software development, debugging practices, and the ability to implement scripts and automated tests to effectively execute the six-phase bug diagnosis process.

What is the best way to narrow down a complex codebase issue during debugging?▼

The best way to narrow down a complex codebase issue is to systematically hypothesize, instrument the code to gather targeted data, and use a minimized reproduction case to isolate the exact failure point.

Why should I include a post-mortem and cleanup phase after fixing a bug?▼

You should include a post-mortem and cleanup phase after fixing a bug to remove temporary debugging instrumentation, document the root cause, and prevent similar regressions in future development.