Principle Migrate Callers Then Delete Legacy Apis
- 404 installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
When deprecating an endpoint, SDK method, or internal API, migrate every caller to the replacement surface before removing the legacy contract.
About
Teaches a safe API deprecation workflow: locate every caller of a legacy interface, move each to the new API, confirm zero remaining references, then delete the old surface so refactors do not break downstream services or clients.
- Inventory all callers first
- Ship replacement before removal
- Avoid breaking silent consumers
- Stage dual-run if needed
- Delete legacy only when unused
Principle Migrate Callers Then Delete Legacy Apis by the numbers
- 404 all-time installs (skills.sh)
- Ranked #1,073 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill principle-migrate-callers-then-delete-legacy-apisAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 404 |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
What it does
When deprecating an endpoint, SDK method, or internal API, migrate every caller to the replacement surface before removing the legacy contract.
Files
Migrate Callers Then Delete Legacy APIs
When we decide a new API is the right design, migrate callers and remove the old API in the same refactor wave instead of preserving compatibility layers.
Rule:
- Do not keep legacy API paths alive only because internal callers still exist
- Inventory callers, migrate them, and delete the old API immediately
- Treat temporary adapters as exceptional and time-boxed, not default architecture
- 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
Keeping both old and new APIs creates dual-path complexity, slows cleanup, and makes the codebase feel append-only.
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198k