API Change Safety Net
v0.3.1 · 12 Nov 2026 · MIT · Backend
Catches regressions when you change an existing endpoint. The agent writes a failing test for the old behaviour before it touches the fix, so a broken contract surfaces as a red test instead of a 500 in production.
Sample report
Claude Code · Codex · Cursor · Windsurf
api-change-safety-net v0.3.1Download SKILL.mdpinned version · no account needed · drop the file in your agent's skills folder
Sample data
36
runs · 6 tasks × 3 reps × 2
8/18
baseline (44%)
10/15
with pack (67% of attempted · 3 correctly idle)
1
regression kept in report
Sample data
Tasks
| Task | Baseline | With pack | Verdict |
|---|---|---|---|
| endpoint-edit | 2/3 | 3/3 | Improved |
| add-query-param | 1/3 | 2/3 | Improved |
| rename-field | 1/3 | 2/3 | Improved |
| deprecate-route | 2/3 | 1/3 | Regression |
| add-middleware | 2/3 | 2/3 | No change |
| change-response-shape | 0/3 | 3 idle | Correctly idle |
Full run log: release report pp-2026-1112-034 (sample data).
Versions
0.3.1 · 12 Nov 2026 - Fixes the header case mismatch
0.3.0 · 4 Nov 2026 - Adds the middleware task
0.2.0 · 21 Oct 2026 - First public evidence report
What it does not do
Does not write the fix
Does not run your suite
Only proves the old behaviour first, then gets out of the way
Kept failure - deprecate-route regressed: with the pack, 2 of 3 runs missed the docs update. Kept in the report, not hidden - fix planned for v0.3.2. Legacy DELETE 500 stays documented, not fixed. Run 14 timeout was a flake; the rerun passed.