Fix a bug test first - reproduce it in a failing test, fix, watch the test pass, and stop after three failed attempts to rethink. Use for any reported bug or failing behaviour.
Installs into .claude/skills of the current project.
Are you the author of Bug Fix?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/fadi88-bug-fix-one-man-startup)
---
name: bug-fix
description: Fix a bug test first - reproduce it in a failing test, fix, watch the test pass, and stop after three failed attempts to rethink. Use for any reported bug or failing behaviour.
---
# Bug fix
1. **Find the row.** Which requirement does the bug break? If none, the bug is a missing
requirement: write the row first.
2. **Reproduce in a test** that fails for the reason the user saw. Watch it fail. A fix without a
failing test first is a guess.
3. **Measure before theorising.** Read the actual values, logs and inputs. The plausible cause
is often not the cause.
4. **Fix** the smallest thing that makes the test pass without weakening any other test.
5. **Watch it pass,** then run the sweep.
6. **Three strikes.** After three fixes that did not work, stop changing code. Write down what you
know, what you tried and what each attempt showed, and hand it to the orchestrator. The fourth
blind attempt is the one that breaks something else.
7. **Grep for siblings.** The same mistake usually lives in more than one place.
