Does this skill provide the final code fix?

Its primary purpose is diagnosis. Once the cause is found with high confidence, it provides a 'handover package' that contains the minimum info needed to start the solution phase.

How does this skill help with debugging?

It enforces a structured 'Hypothesis -> Evidence' loop that prevents 'shotgun debugging' by requiring verifiable proof before proposing fixes.

What information is needed to start a diagnosis?

You need to provide a 'clear output' which includes a minimal reproduction case, acceptance criteria for the fix, and any existing evidence like logs.

Why is there a limit of 5 hypotheses?

To maintain focus and minimize token usage, the skill prioritizes the most likely causes rather than listing every theoretical possibility.

How long should verification steps take?

Each verification action is designed to be completed in under 10 minutes to ensure a rapid feedback loop and quick time-to-resolution.

Bug Diagnosis & RCA

Name: Bug Diagnosis & RCA
Author: xiaxingxiaowei1983

byxiaxingxiaowei1983

0•

보안 및 테스팅

Facilitates rapid root cause analysis by guiding Claude through evidence-based hypothesis testing and systematic debugging.

The Bug Diagnosis skill transforms the troubleshooting process from trial-and-error into a structured, evidence-based methodology known as Hypothesis-Evidence-Location. By enforcing a disciplined workflow, it helps developers identify the exact point of failure within a system while minimizing unnecessary code changes and token usage. The skill generates a prioritized list of up to five verifiable hypotheses, creates a clear plan for testing each, and provides a confidence-rated diagnosis. This ensures that every diagnostic step is focused, measurable, and completed quickly, moving the developer from investigation to resolution with high certainty.

주요 기능

01Structured verification plans with expected evidence and counter-signals

02Confidence-rated diagnostic reporting with evidence citations

03Standardized handover package for transitioning to solution implementation

04Hypothesis-driven root cause analysis (RCA) framework

05Strict token-optimized output focusing on top 5 hypotheses

060 GitHub stars

사용 사례

01Identifying regressions in legacy codebases without clear error logs

02Isolating the source of intermittent production failures

03Locating logic errors in complex multi-layered system architectures

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add xiaxingxiaowei1983/openclaw bug-diagnosis

For use in Claude.ai and ChatGPT

주요 기능

01Structured verification plans with expected evidence and counter-signals

02Confidence-rated diagnostic reporting with evidence citations

03Standardized handover package for transitioning to solution implementation

04Hypothesis-driven root cause analysis (RCA) framework

05Strict token-optimized output focusing on top 5 hypotheses

060 GitHub stars

사용 사례

01Identifying regressions in legacy codebases without clear error logs

02Isolating the source of intermittent production failures

03Locating logic errors in complex multi-layered system architectures

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add xiaxingxiaowei1983/openclaw bug-diagnosis

For use in Claude.ai and ChatGPT