migration-loop

A configuration of [loop-controller]. That skill supplies the loop machinery — primitive selection, the full guardrail stack, state externalization. This skill supplies the two things specific to "migrate a fixed set of targets to completion": a default-FAIL target checklist driven one entry per iteration, and a proof that no legacy pattern remains (a grep for the old pattern returning zero), not merely "tests pass." Read loop-controller for the guardrails; they're inherited, not repeated here.

Why disable-model-invocation: this loop edits and commits code on its own — a checkpoint commit per migrated target — until the whole set is done. You want to type /migration-loop (or have the orchestrator dispatch it) — not have Claude silently start rewriting every file because it noticed an old API.

The 5-part contract