diagnose

Reproduce software failures and isolate root causes with hypothesis testing.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/babually/bongo-template --skill diagnose-babually
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/babually/bongo-template/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/babually/bongo-template --skill diagnose-babually

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose difficult bugs and performance regressions by turning vague symptoms into a structured, reproducible investigation. It is designed to reduce guesswork and move quickly from failure to root cause.

Core Features & Use Cases

  • Build a feedback loop: Create a fast, deterministic repro using tests, scripts, browser automation, or harnesses.
  • Reproduce and narrow: Confirm the exact failure mode, then minimise the scenario until the cause becomes clearer.
  • Hypothesise and instrument: Rank falsifiable explanations, add targeted probes, and compare predictions one at a time.
  • Fix and lock it in: Add a regression test at the correct seam, verify the fix, and clean up debug instrumentation.
  • Use case: A React page crashes only sometimes after a recent change; this Skill helps reproduce it, isolate the triggering condition, and verify the repair.

Quick Start

Use the diagnose skill to reproduce the bug, propose ranked hypotheses, and build a minimal failing test or script that proves the root cause.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I find the root cause of an intermittent bug?▼

Diagnosing a flaky failure requires building a deterministic feedback loop that reproduces the exact failure mode, then isolating the root cause through disciplined hypothesis testing and targeted instrumentation.

What is the best way to debug a performance regression in an HTTP service?▼

Debugging a performance regression involves reproducing the failure deterministically, minimizing the scenario, proposing ranked hypotheses, and adding targeted probes to compare predictions until the root cause is isolated.

How do I reproduce a browser flow crash that only happens sometimes?▼

Reproducing an intermittent browser flow crash requires creating a fast, deterministic repro using browser automation or scripts, confirming the exact failure mode, and minimizing the scenario until the triggering condition becomes clearer.

Can I use hypothesis testing to isolate software defects in CLI tools?▼

Yes, isolating software defects in CLI tools uses disciplined hypothesis testing by ranking falsifiable explanations, adding targeted probes, and comparing predictions one at a time to pinpoint the exact root cause.

What should I do after isolating a bug to prevent future regressions?▼

After isolating a bug, add a regression test at the correct seam to verify the fix, clean up any debug instrumentation used during diagnosis, and lock in the repair to prevent future recurrence.