Command
/shipmates-migrate
discover → transform each → verify → sweep clean
Find every call site, rewrite them, leave none of the old pattern.
See it run
/shipmates-migrate runs, in order.How to run it
Run it in your harness
/shipmates-migrate <from → to — e.g. "moment.js → date-fns" or "callback API → async/await"> [sequential] [board=epic-deferred | board=off]<angle brackets> = required · [square brackets] = optional
How it works
Engineers rewrite in parallel batches. SDET proves the old pattern is gone. The same review board as /shipmates-ship-issue then sits — extra seats from the same flags.
Census
Find every occurrence. Miss one and the migration is not done.
No specialist — the run must see every call site.
Rewrite
Several engineers, disjoint files, in parallel. Non-mechanical sites are handled one by one, not blind-replaced.
Crew
Land
Two reviewers sit on the first pushed head. After a fixer, failers sit again and a prior ACCEPT carries unless the delta can invalidate it.
Also sit when
architectnew subsystem, schema, or a change that crosses many modulesux-ui-designeron-screen UI — screens, flows, componentsart-directorrendered art (games, illustration), not app chromesdetthe plan asks for a specialist test reviewdevops-engineerpipeline, images, or how the project shipstechnical-writerdocumented behaviour or a public API/CLI
Shared machinery — how commands work: worktrees, the CI gate, the review board, and merge modes.
When to use
- An API, library, or idiom must change everywhere it appears.
- Behaviour stays, shape changes? /shipmates-refactor. Choice still open? /shipmates-spike.
The skill
The installer ships the full skill — stages, gates, config — from commands/shipmates-migrate.md.