domains / families / software-engineering / what-could-break
what-could-break
authentic
Find what a change breaks outside its own diff, then prove the one fact that makes it safe by running real code. Use before any multi-file edit or an edit to a shared path.
When to use
- Use before any multi-file edit, or an edit to a shared path: API payload, config, stored data, a client other apps read, a prompt or policy file
- Use when the user asks "what could this break" or "blast radius of X"
- Use for a small diff you do not trust
- Use when a brief asserts something about existing code, before you design against that assertion
When not to use
- A risk needs a real chance and a real cost, or it does not belong on the list.
- A search that found nothing is still an answer: write the search down rather than claiming the risk does not exist.
- This skill does not replace environment-specific testing or expert review.
- Keep secrets and private data out of the report and out of any script left behind.
Skill page
Source