fix-bug

Diagnose bugs through a gated RCA, brainstorm, implement, and walkthrough workflow.

1|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/akashjpal/question-generator --skill fix-bug-akashjpal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-bug
Source: https://github.com/akashjpal/question-generator/tree/main/.claude/skills/fix-bug
Command: npx skills add https://github.com/akashjpal/question-generator --skill fix-bug-akashjpal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug fixes often skip root cause analysis and jump straight to patching code, leading to regressions and undocumented decisions. This Skill enforces a four-stage gated process so every fix is diagnosed, approved, tracked, and explained before and after implementation. ## Core Features & Use Cases - Root Cause Analysis: Produces an RCA_Bug_<ShortName>.md document capturing symptom, root cause with file:line references, evidence, and blast radius. - Approval-Gated Implementation: Brainstorms multiple candidate fixes with trade-offs, requires explicit user approval of one approach, then implements against a tracked todo.md checklist. - Plain-Language Walkthrough: Writes a short walkthrough document with a mermaid diagram explaining what broke and how it was fixed. - Use Case: A user pastes a stack trace from a failing autosave feature; the Skill produces an RCA, presents two or three distinct fix options, implements the approved one step by step, and delivers a walkthrough a teammate can read in two minutes. ## Quick Start Ask the assistant to fix the bug you just observed and paste the error message or stack trace to begin the diagnosis stage.

Frequently Asked Questions about fix-bug

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

FAQPage Schema
How do I fix a bug with root cause analysis documentation?▼

Report the bug or paste the error, and the Skill writes an RCA document capturing symptom, root cause with file:line references, evidence, and blast radius before any code changes. Implementation only begins after you approve one of the proposed fixes.

How to get multiple fix options before changing code?▼

After diagnosis, the Skill invokes a brainstorming step that generates genuinely distinct candidate fixes with trade-offs covering correctness, blast radius, and complexity. You explicitly approve one approach via a question prompt before implementation starts.

What artifacts does this bug fix workflow produce?▼

It produces three markdown files: RCA_Bug_<ShortName>.md for the diagnosis, todo.md tracking implementation steps with pending/in-progress/done states, and <ShortName>_walkthrough.md with a plain-language explanation and mermaid diagram.

Can the fix start immediately without my approval?▼

No. The workflow is gated: no implementation code is written until you explicitly approve exactly one of the brainstormed candidate fixes. If the choice is ambiguous, the Skill asks rather than assumes.

When should I not use this structured bug fix process?▼

The four-stage process is heavyweight for trivial one-line typos or obvious configuration mistakes where a full RCA and walkthrough add no value. It is designed for bugs where the root cause is unclear or the fix has meaningful trade-offs.