Fan out a migration
Plan a repetitive change across many files.
Official basis Fan out across files for large, mechanical migrations. docs ↗
The prompt
List every file that needs the <X → Y> migration, and for each one describe the exact change. I'll then run you over each file with a scoped, tightly-permissioned command — for now, just produce that per-file plan.Why it works
Big mechanical migrations go faster as many small, isolated jobs than one giant session. Getting the file list and per-file change first lets you parallelize (e.g. headless runs) with confidence.
Fill in
<X → Y>— the migration (e.g. CommonJS → ESM).
Follow-ups
- “Start with the 5 lowest-risk files so we can validate the pattern.”