Codebase-wide migrations
Send the upgrade notes with a few typical call sites, and have Claude Opus 5.5 find every pattern that needs to change, show the new form, and plan the order of batched commits. For big changes, run the related tests on each batch before merging.
Example: Which calls does this dependency upgrade break?
Material
- package.json
- "date-lib": "^2.4.0" upgraded to "^3.0.0".
- Upgrade notes
- In v3, the second argument of format() changes from a string to an object { pattern }.
- src/report.ts
- const month = format(date, "YYYY-MM");
PromptUsing the upgrade notes, find the calls in the sample code that need to change, write the updated code, and lay out how to finish the migration across the repo in batches.
Sample answer · written by hand to show the reasoning
The call in report.ts becomes format(date, { pattern: "YYYY-MM" }). Search the repo for every format( call and batch them by directory. After each batch, run the report tests and confirm the date strings match the pre-upgrade output before merging the next one.