skills.rest
stephangrobler
stephangroblerCOMMUNITY
Explore all skills by this author →
Website𝕏@stephanfxGitHub

diagnosing-bugs

Diagnose software bugs and performance regressions through systematic hypothesis testing and instrumentation.

Updated Aug 23, 2026
Search Tags:#hypothesis testing#instrumentation#bug diagnosis#debugging process#performance regression
One-click install
npx skills add https://github.com/stephangrobler/myBpmFlow --skill diagnosing-bugs-stephangrobler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/stephangrobler/myBpmFlow/tree/main/agent/skills/diagnosing-bugs
Command: npx skills add https://github.com/stephangrobler/myBpmFlow --skill diagnosing-bugs-stephangrobler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a systematic approach to diagnose hard bugs and performance regressions, streamlining the debugging process and improving efficiency.

Core Features & Use Cases

  • Diagnosis Loop: Offers a structured feedback loop for debugging, including various methods like bisection, hypothesis-testing, and instrumentation.
  • Minimal Reproducible Scenario: Helps minimize the bug to the smallest scenario that still goes red, simplifying the hypothesis generation phase.
  • Hypothesis Testing: Encourages generating 3-5 falsifiable hypotheses before testing, improving the debugging process.
  • Instrumentation: Provides guidance on effective instrumentation techniques for debugging, including debugging tools and logging strategies.
  • Regression Testing: Ensures that the bug is fixed and that a regression test is in place before declaring the bug resolved.

Quick Start

To diagnose a bug, use the 'diagnosing-bugs' skill and follow the structured debugging phases outlined in the skill's instructions.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I systematically debug hard bugs and performance regressions?▼

To debug hard bugs and performance regressions systematically, follow a structured diagnosis loop: reproduce and minimize the bug, generate 3-5 falsifiable hypotheses, instrument for debugging, apply the fix, and implement regression tests.

What is a minimal reproducible scenario and how does it help with bug diagnosis?▼

A minimal reproducible scenario is the smallest test case that still triggers the bug. Minimizing the bug to this smallest scenario simplifies hypothesis generation and accelerates the overall debugging process.

How do you use hypothesis testing when diagnosing software bugs?▼

Hypothesis testing for bug diagnosis involves generating 3-5 falsifiable hypotheses about the bug's cause before testing them. This structured approach prevents trial-and-error debugging and streamlines finding the root cause.

What is the best way to instrument an application for debugging?▼

The best way to instrument for debugging involves applying effective logging strategies and utilizing debugging tools to build a feedback loop, allowing you to trace execution and validate hypotheses during bug diagnosis.

Why do I need regression tests after fixing a performance regression?▼

You need regression tests after fixing a performance regression to ensure the bug is permanently resolved and does not reappear in future code changes. A bug is only declared resolved when a regression test is in place.

Related Skills

Explore More Software Engineering Skills→
Ilenburg1993Ilenburg1993
3

reactive-bug-audit

Analyze stack traces and logs to identify root causes and apply minimal patches.

Community
Intermediate
eng-vmessiaheng-vmessiah
2

ai-regression-testing

Automate regression tests validating API response shapes and state integrity.

Community
Intermediate
LuizEduPPLuizEduPP

debugging-strategies

Reproduce, diagnose, and resolve bugs using structured debugging workflows.

Community
Advanced
faroukBakarifaroukBakari
5

debug-hypothesis

Organize hypothesis-driven debugging to isolate root causes of software failures.

Community
Advanced