change-without-breakinglisted
Install: claude install-skill RabbitDesigns22/change-without-breaking
# Change without breaking
An agent asked to fix one thing often breaks two others. The fix itself is usually right. What goes wrong is everything around it: a caller nobody searched for, a rule that now fires on the wrong input, a test quietly loosened until it passed, a job that resends forever, a migration that touched more rows than anyone checked.
Real cases this skill was built from, all in one week of fixing live apps:
- **A "ready to buy" rule** treated questions like "how long does one box last?" as a purchase decision.
- **A health-risk detector** blocked a sale because the customer wrote "muscle mass".
- **A new reminder** was about to resend every 15 minutes, forever.
Each one passed its own happy-path test.
The goal of this skill: **everything that worked before the change still works after it, and you can prove it.**
Companions: `blast-radius` digs deeper into what one diff can break, `working-with-legacy-code` covers untested code, and `shipping-and-launch` covers staged rollouts.
## 0. Size it
- **Tiny and local** (a typo, a label, one line nobody else calls): do steps 1, 4 and 7, and run the tests that exist.
- **Everything else:** all steps. The more people or data it touches, the more of step 9 applies.
## 1. Do-not-change list and checkpoint
Before the first edit:
- Write 3-6 lines:
- what you are changing (one thing);
- what must stay exactly the same;
- how you go back.
- Make a checkpoint you can return to in one command: note the current co