principle-migrate-callers-then-delete-legacy-apis from barbieri/local-openfinance is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 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.
The line at the top of this page pins the label git:20261005.32edae5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_bo2giq3hkqnkgkel
GET https://markdownregistry.com/api/v1/resolve?ref=barbieri/local-openfinance/principle-migrate-callers-then-delete-legacy-apis
GET https://markdownregistry.com/api/v1/blob/09978915a4a11990cf0a9a02d9c08cc59e0b7a04c5c24b83aa560fbe4146f75b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
barbieri/local-openfinance · .agents/skills/agent-browser/SKILL.md · Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages…
barbieri/local-openfinance · .agents/skills/ai-sdk/SKILL.md · Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK…
barbieri/local-openfinance · .agents/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
barbieri/local-openfinance · .agents/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
barbieri/local-openfinance · .agents/skills/automate-me/SKILL.md · Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a…
barbieri/local-openfinance · .agents/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
barbieri/local-openfinance · .agents/skills/cancel-ralph/SKILL.md · Cancel an active Ralph Loop. Use when the user wants to stop, cancel, or abort a running ralph loop.
barbieri/local-openfinance · .agents/skills/cli-for-agents/SKILL.md · Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples…
barbieri/local-openfinance · .agents/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
cursor/plugins · pstack/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md · Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
cursor/plugins · harness/pstack/claude-code/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md · Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
nightly-labs/openbot · marketplace/production-catalog/bundles/pstack/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md · Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md · Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
backnotprop/pstack · skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md · Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
iap/pstack-hermes · skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md · Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/migrate-callers-then-delete-legacy-apis/SKILL.md · Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the…
theonlyfusioncube/potetos-for-everyone · skills/principle-migrate-callers-then-delete-legacy-apis/SKILL.md · Move callers to the new shape and delete the old path in the same migration wave instead of carrying a compatibility…
