agentleFS
christofferbergjchristofferbergj/agent-skills/skills/principles/principle-migrate-callers-then-delete-legacy-apis/SKILL.md

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

Skill1 starsChanged 26 days agoMITView on GitHub

Choose migration strategy when an API or schema replaces an old contract: coordinated caller migration and deletion, or staged coexistence for real compatibility or release obligations.

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, poteto-help and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 32 projects that use this

  • shiwenbin1617Skill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 17 projects that use this

  • JoshueOsunaSkill

    Poteto Mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Update tests for the accepted contract.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Migrate callers then delete legacy APIs

This owner chooses migration strategy and verification boundaries for both Matt's ticket flow and Pstack playbooks.

  1. Inventory all callers and compatibility obligations, including external consumers, independently deployed versions, stored data, and rollout or rollback requirements. Complete when the old contract's consumers and required lifetime are known.
  2. If callers are internal and the project can absorb a coordinated change, migrate every caller and delete the old API in one verification unit. Existing internal callers alone do not justify a compatibility layer. Several bounded tickets can contribute to that unit on an isolated integration branch. Complete when the plan covers every caller, obsolete-path deletion, and the unit's checks.
  3. Use expand-contract only when a real compatibility obligation or required independently green release makes coexistence necessary. Add the new form, migrate consumers in checked batches, and remove the old form after the obligation ends. Give every temporary adapter a removal condition and an owning ticket. Complete when the reason for coexistence and its exit gate are explicit.
  4. Declare the checks for each ticket or migration phase and the final integration unit. Planned, scoped, reversible breakage may exist inside an isolated unit; passing phase checks can unblock the next ticket inside it. Work outside that unit remains blocked until its full static, runtime, and contract checks pass. Preserve an already-approved rollout contract; seek a decision before changing it. Complete when intermediate progress and final acceptance cannot be confused.
  5. Update tests for the accepted contract. Preserve distinct behavioral regressions while deleting tests that only protect the retired implementation. Complete when the caller inventory is exhausted, required compatibility is honored, obsolete paths are removed at their declared gate, and the final unit's checks pass.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.