diagnosing-bugs

Diagnose software bugs and performance regressions through structured reproduction workflows.

Updated Aug 26, 2024

Search Tags:#debugging #root cause analysis #regression testing #bug diagnosis #reproduction #performance regression

Ready to run

npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill diagnosing-bugs-fabiendehopre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/FabienDehopre/my-netatmo-24/tree/main/.agents/skills/diagnosing-bugs
Command: npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill diagnosing-bugs-fabiendehopre

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers diagnose difficult bugs and performance regressions by replacing guesswork with a disciplined reproduction and investigation workflow.

Core Features & Use Cases

Feedback Loop Construction: Builds tight, deterministic reproduction loops using tests, scripts, traces, or harnesses that expose the exact failure.
Root Cause Investigation: Guides hypothesis ranking, targeted instrumentation, minimization, and validation before applying fixes.
Regression Prevention: Establishes regression tests, cleanup steps, and post-mortems to prevent recurring issues.
Use Case: When an application intermittently fails, becomes slow after a change, or produces unexpected behavior, use this Skill to isolate the cause and verify the repair.

Quick Start

Use the diagnosing-bugs skill to investigate the reported failure, create a reproducible test loop, and identify the root cause.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema

How do I find the root cause of intermittent software failures?▼

To find the root cause of intermittent failures, construct deterministic reproduction loops using tests, scripts, or traces to expose the exact failure, then apply hypothesis-driven analysis and targeted instrumentation to isolate the issue.

What is the best way to debug a performance regression after a code change?▼

Debugging a performance regression requires building a tight feedback loop that reproduces the slow system behavior, ranking hypotheses, and validating the fix through targeted instrumentation before establishing regression tests.

How do I systematically diagnose a failing test in a complex codebase?▼

Systematically diagnose a failing test by replacing guesswork with a structured investigation workflow: create a reproducible test loop, rank potential hypotheses, minimize variables, and validate the root cause before applying fixes.

Does hypothesis-driven analysis work for reproducing hard bugs?▼

Hypothesis-driven analysis works for reproducing hard bugs by guiding targeted instrumentation and minimization within a deterministic feedback loop, ensuring you validate the exact failure conditions before attempting a repair.

How do I prevent bug regressions after fixing a broken feature?▼

Prevent bug regressions by establishing dedicated regression tests within your reproduction loop, verifying the repair resolves the failure, and performing cleanup steps or post-mortems to document the investigation.