Principle Migrate Callers Then Delete Legacy Apis
Apply when introducing a new internal API while old callers still exist.
by michael-denyer · MIT
The skill
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
Migrate Callers Then Delete Legacy APIs
- Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details
When this applies:
- No external users depend on backward compatibility
- The project can absorb coordinated breaking changes
- The new API is part of a simplification or refactor initiative
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: michael-denyer/principle-migrate-callers-then-delete-legacy-apis-33898200162.
Details
- Publisher
- michael-denyer
- Category
- Software Development › APIs & backend
- License
- MIT
- Updated
- 2026-10-18
References
More from michael-denyer
- Architect Sketch types, signatures, and module structure before code, then stay in the loop while implement…
- Arena Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the loser…
- Automate Me Use for \"automate me\", \"create/update/refresh my -mode skill\", \"turn/capture my preferences…
- Babysit Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a…