Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cursor/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.
Passed 23 of 23 test cases with the skill, and 3 of 23 without it.
and 41 more in the full report
20 fixed3 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 20 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are updating an internal GraphQL resolver helper `formatResponse(data)` to `buildResolverContext(data)`. The codebase is entirely internal. Should we keep a bridge adapter for `formatResponse`? Detail the plan for callers, helper file, and tests.
| Checked | Without skill | With skill |
|---|---|---|
| Advises migrating callers to `buildResolverContext` in a single refactor pull request. | Passed | Passed |
| Recommends deleting `formatResponse` instead of creating bridge adapters. | Passed | Passed |
| Advises removing tests that only verify internal mechanics of `formatResponse`. | Missed | Passed |
The instructions your model reads when the skill loads.
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:
When this applies:
Keeping both old and new APIs creates dual-path complexity, slows cleanup, and makes the codebase feel append-only.
test cases passed, vs 3 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.