Triage upgrades and move major ones in stages
Kent C. Dodds used Cursor to organize site dependency work, then carried out a Remix v2 to React Router v7 migration and related updates.
- What they did
- Kent asked Cursor to inspect his site and sort the outdated packages by how much work each upgrade would likely take. He then opened separate sessions for the different tiers: quick fixes first, then moderate updates, then the big migrations one at a time. Before changing xstate and Remix, he had the agent consult the migration guides. The React Router v7 move ran as a background job, with Kent answering its questions and sharing route information so it could verify the new setup.
- How it went
- The project update went well overall. One routing issue appeared after moving to react-router-auto-routes, and that part needed another fix. The whole migration took about a day, changed more than 17k lines, and eventually went in after several BugBot and CodeRabbit correction passes.
- Tips
- This kind of task benefits from good tests and solid docs already in the project. It also helps to give the agent a way to cross-check its work against known output, such as route listings.
Try it yourself with Cursor
Check the official migration guide for moving [package/framework] from [current version] to [target version]. Then review the outdated packages in my project and group them by how difficult or risky each upgrade appears. Work through them in order: smallest changes first, then medium ones, then major migrations one at a time. For [specific dependency], read the migration docs before editing code. After each step, run the relevant tests and show me the changes. If any step would delete files, submit forms, send messages, make purchases, or create a commit, stop and ask for my approval before continuing. Also compare any route list or other generated output with the expected result so you can catch mismatches early.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Turn saved bookmarks into quick demo builds
A daily bookmark check can feed Cursor a new tech idea and produce a prototype after approval.
Use Cursor to make a custom invitation site
Fabio Zapata had Cursor assemble a local invitation site with motion, images, and page links, using prompts instead of hand-coding at first.
Flag coding conflicts before agents edit
They set up a local layer that makes coding agents announce planned changes so overlapping architecture work gets caught early.
Assign PRs and bug fixes across Cursor sub-agents
A Cursor coordinator tracked incoming pull requests and live bugs, sent sub-agents after each issue, and kept the user updated along the way.
Automate large service upgrades with self-checking agents
Brex used Cursor agents to let one engineer update 180 microservices to a newer Micronaut release in roughly a month.
Have agents co-build a reference system with role splits
A solo founder divided an AI-assisted build into roles and shipped a 120-model mental-models framework with an MCP server.