← LeaderboardThe Skill Leaderboard

principle-migrate-callers-then-delete-legacy-apis

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.

Published by michael-denyer ↗michael-denyer/pstack-claude

Try your first task

principle-migrate-callers-then-delete-legacy-apis

Start a fresh conversation. Replace the highlighted placeholders.

Use principle-migrate-callers-then-delete-legacy-apis to For [new internal API], inventory and migrate all callers, remove the legacy API and its obsolete tests, and update tests to assert the new contract, provided no external users depend on backward compatibility.

Required inputs

  • [new internal API]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: principle-migrate-callers-then-delete-legacy-apisdescription: "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."user-invocable: false

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