bug-root-cause-analysis

Diagnose bugs through a reproduce, isolate, fix, and validate workflow.

1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/tanveerriaz/Skillz --skill bug-root-cause-analysis-tanveerriaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-root-cause-analysis
Source: https://github.com/tanveerriaz/Skillz/tree/main/skills/bug-root-cause-analysis
Command: npx skills add https://github.com/tanveerriaz/Skillz --skill bug-root-cause-analysis-tanveerriaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Under time pressure, developers and AI agents patch the first suspicious line of code, which masks defects and creates regressions. This Skill enforces a disciplined debugging loop so the actual root cause is found and fixed, with proof the fix works before the bug is closed. ## Core Features & Use Cases - Structured Debugging Loop: Follows a reproduce → isolate → hypothesize → confirm → fix → validate procedure so no step is skipped. - Edge Case Handling: Covers intermittent heisenbugs, environment-specific failures, and bugs with multiple contributing causes. - Safety Guardrails: Prohibits closing bugs without re-running reproduction, disabling tests to pass builds, and speculative shotgun changes. - Use Case: Given a 500 error on a checkout endpoint, reproduce it with an empty cart, isolate the divide-by-zero in the total calculation, apply a minimal guard fix, and add a regression test proving the symptom is gone. ## Quick Start Investigate this error and find the root cause using the reproduce, isolate, diagnose, fix, and validate loop before making any code changes.

Frequently Asked Questions about bug-root-cause-analysis

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

FAQPage Schema
How do I find the root cause of a bug instead of just fixing the symptom?▼

Reproduce the bug reliably first, then isolate the failing layer, input, or commit using bisection or minimal test cases. Form a hypothesis, confirm the underlying cause by asking why until a change would prevent the bug, then apply the smallest fix targeting that cause.

How to debug a bug that works locally but fails in production?▼

Compare configuration, dependency versions, data, and permissions between environments before touching application logic. Environment-specific bugs are usually caused by these differences, so document the factors once identified.

What should I do when a bug cannot be reproduced?▼

Do not change code blindly. Add logging and observability to gather the conditions under which the failure occurs, then collect more data until reliable reproduction steps are established.

How do I debug intermittent bugs that only happen sometimes?▼

Intermittent heisenbugs usually indicate race conditions, ordering issues, or shared state. Reproduce them under load or with modified timing, then isolate the concurrency or state-management cause before fixing.

When is it acceptable to close a bug after applying a fix?▼

Only after re-running the original reproduction and confirming the symptom is gone. A regression test that would have caught the bug should be added, and nearby flows checked for unintended side effects.