rb-diagnose

Diagnose software defects through reproducible experimentation and automated verification tests.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/richardmbailey/rb-skills --skill rb-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rb-diagnose
Source: https://github.com/richardmbailey/rb-skills/tree/main/rb-diagnose
Command: npx skills add https://github.com/richardmbailey/rb-skills --skill rb-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of inefficient, reactive debugging by providing a structured, evidence-based framework for investigating bugs, regressions, and flaky tests.

Core Features & Use Cases

  • Structured Investigation: Guides the user through a rigorous procedure from reproducing the failure to identifying the root cause.
  • Regression Prevention: Ensures that every fix is validated by an automated regression test, preventing the recurrence of defects.
  • Use Case: When a production system reports a mysterious intermittent failure, use this skill to isolate the specific environment variables and seeds causing the issue, ensuring a permanent fix rather than a temporary patch.

Quick Start

Invoke the rb-diagnose skill to begin a systematic investigation of the current failing test case and document the findings in your working diary.

Frequently Asked Questions about rb-diagnose

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

FAQPage Schema
How do I perform root-cause analysis for intermittent flaky tests?

Root-cause analysis for flaky tests requires a systematic framework to isolate specific environment variables and seeds through reproducible experimentation, ensuring a permanent fix rather than a temporary patch. This approach validates fixes using automated regression tests.

What is the best way to debug mysterious software regressions in complex codebases?

Debugging software regressions in complex codebases is best handled through evidence-based hypothesis testing, guiding you from reproducing the failure to identifying the root cause and implementing automated verification tests to prevent recurrence.

How do I systematically troubleshoot code defects instead of applying temporary patches?

Systematic troubleshooting of code defects demands a structured investigation framework that moves from reproducing the failure to root-cause isolation, ensuring every fix is validated by an automated regression test for long-term regression prevention.

Can I use a structured debugging framework for production system failures?

A structured debugging framework applies to production system failures by guiding you through rigorous evidence-based hypothesis testing to isolate the exact environment variables causing the issue, ensuring a permanent fix validated by automated tests.

When do I need to implement automated verification tests for software defects?

Automated verification tests for software defects are required immediately after identifying and fixing the root cause, serving as regression tests to validate the fix and prevent the recurrence of defects in complex codebases.