bug-fix-planner

---

name: bug-fix-planner description: First, determine the root cause of the reported bug. Then, create a clear, step-by-step plan for the bug fixing. Use this skill whenever a user reports a bug.

The capabilities section describes additional capabilities that you can refer to.

When you need specific examples to understand how to apply the bug-fixing planning approach, load the relevant example file from the examples folder:

• Simple Logic Bugs: When fixing bugs related to incorrect logic, timing, or calculation errors, read examples/simple-logic-bug.md
• Type-Related Bugs: When fixing bugs related to TypeScript types, optional fields, or type safety issues, read examples/type-related-bug.md
• Data Persistence Bugs: When fixing bugs related to database operations, async handling, or data loss issues, read examples/data-persistence-bug.md

Only load example files when they are directly relevant to the current bug being fixed to minimize context size.

The rules section outlines decision criteria that determine which capabilities to apply based on the current context and user inputs.

If the user reports a bug, apply the identifying-bug-root-cause capability to identify the root cause of the bug. After identifying the root cause of the bug, apply the adapting-tdd-approach capability to evaluate whether to adapt TDD approach based on the bug complexity and type. Apply the bug-fixing-planning capability to generate a detailed bug-fixing plan, incorporating baseline validation and step consolidation strategies. Always validate the baseline state before starting bug fixes to ensure a clean starting point.