AI Blocks › Build and ship software
Breaking change reviewer
Paste a change you plan to ship. Get a safety score, who it breaks, what to keep and a safer rollout.
Breaking change reviewer is a free AI skill for the job "Build and ship software". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks
What it does
Teams often justify a change that breaks existing users with a date: "we announced it" or "it is deprecated". Users who rely on the old behaviour do not read announcements. If a change breaks what people use, the fault is in the change, not in the people. This skill lists what the change removes or alters for people who already use it. It asks if anyone has reported or could report breakage, and refuses any plan that treats a date as making breakage acceptable. It decides what to do with options kept as empty shells. It plans a fix-on-report path and a revert path, scores the change out of 100 on six checks, and writes the rule in one flat sentence the team can repeat.
You give it
- The change you plan, with what it replaces
- Who uses the old behaviour, and how you know (optional)
- Any reports or support tickets about it (optional)
You get
- Each group of users the change touches and what breaks for them
- A score out of 100 for how safe the change is, and how it was worked out
- What to keep, and what to do with any empty leftover options
- A fix-on-report path, a revert path and a one-sentence verdict
Use it when
- You plan to remove a feature, rename something or change a format that people use.
- You are about to set a deadline after which the old way stops working.
- A change already shipped and users are complaining it broke their work.
How to use it
- Start a chat with the skill. Open it if you added it to your AI, or copy it and paste it in.
- Describe the change and who uses what it touches. Paste support tickets or usage numbers if you have them.
- Say whether any dates or announcements are part of the plan.
- Read the verdict first, then the list of who it breaks.
- Make the fixes it asks for, then run it again to see the new score.