diagnose

Diagnose software bugs and performance regressions through structured hypothesis testing.

Updated Apr 14, 2025

Search Tags:#debugging #hypothesis testing #bug diagnosis #structured analysis #performance regression

Ready to run

npx skills add https://github.com/vladpolewoi/config76 --skill diagnose-vladpolewoi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/vladpolewoi/config76/tree/main/claude/skills/diagnose
Command: npx skills add https://github.com/vladpolewoi/config76 --skill diagnose-vladpolewoi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnose and fix hard bugs and performance regressions efficiently.

Core Features & Use Cases

Disciplined Diagnosis Loop: Follow a structured process to reproduce, hypothesize, instrument, and fix bugs.
Feedback Loop Construction: Create a fast, deterministic pass/fail signal for the bug.
Hypothesis Testing: Generate and test 3-5 ranked hypotheses to identify the root cause.
Instrumentation: Use targeted logs and debuggers to isolate and verify hypotheses.
Regression Testing: Ensure the fix does not introduce new issues.

Quick Start

Use the diagnose skill to initiate a bug diagnosis loop. Provide the reproducible bug scenario and follow the structured steps outlined in the skill.

Frequently Asked Questions about diagnose

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

FAQPage Schema

How do I diagnose complex software bugs using a structured approach?▼

To diagnose complex software bugs, you need a structured approach that constructs a fast feedback loop, tests ranked hypotheses, and uses targeted instrumentation to isolate the root cause efficiently. This ensures a deterministic pass/fail signal for the bug.

What is the best way to troubleshoot a performance regression?▼

Troubleshooting a performance regression requires building a deterministic feedback loop and testing multiple ranked hypotheses. By using targeted logs and debuggers, you can isolate the specific code change causing the performance regression and verify it.

How does hypothesis testing work for bug diagnosis?▼

Hypothesis testing for bug diagnosis involves generating three to five ranked potential root causes. You then use targeted instrumentation and debuggers to test each hypothesis against the reproducible bug scenario until the actual root cause is identified.

Do I need a reproducible bug scenario to use this structured diagnosis loop?▼

Yes, a clear reproducible bug scenario and access to the affected environment or artifacts are required. The structured diagnosis loop depends on a deterministic pass/fail signal to accurately test hypotheses and verify the final fix.

How do I ensure a bug fix does not introduce new issues?▼

To ensure a bug fix does not introduce new issues, you must perform regression testing after isolating the root cause. This verifies that the applied fix resolves the original performance regression or bug without breaking existing functionality.