1
Prompt Devin with the React 19 upgrade guide
React 19 introduces breaking changes across ref handling, context usage, TypeScript types, and removed legacy APIs. The official upgrade guide documents every change, but the hard part is mapping those changes to your code. Instead of reading the guide yourself and auditing every component, hand both to Devin and get back a skill scoped to your actual files.Open a new Devin session from the Devin home page and paste a prompt with the upgrade guide URL and what you need:
2
Layer in codebase-specific context
Devin uses DeepWiki to understand your repo’s architecture automatically. It can also look up online sources about React 19 — the official upgrade guide, blog posts, library changelogs — and incorporate what it finds directly into the skill.To make the skill even sharper, tell Devin about patterns the migration will touch:
- “We use
forwardRefin 23 components undersrc/components/ui/— these are our design system primitives” - “We still have 4 class components in
src/legacy/that use string refs andcomponentWillMount” - “Check other repos in our org (e.g.,
acme/design-system,acme/admin-dashboard) to see if they’ve already started the React 19 migration — reuse any patterns they’ve established”
3
Review the codebase-specific skill
Devin reads the React 19 upgrade guide end-to-end, cross-references every breaking change against your codebase via DeepWiki, and produces a phased skill with specific files, complexity estimates, and validation steps:The skill is a plan, not an executed migration. Review it with your team, adjust the phasing or scope, then decide how to execute.
4
Execute and scale
Once the skill looks right, save it (Devin offers to save it to your organization’s skills) and mention it in a session to execute phase by phase:Scale across repos — If you have multiple React apps that need the same upgrade, ask Devin to run the saved skill across all of them in parallel using managed Devins.

