upgrade-react-navigation — Claude Code skill: major version upgrades

What upgrade-react-navigation does

Reach for this skill when you move React Navigation to a new major version. The agent reads @react-navigation/native in package.json first. On 6.x it opens references/upgrade-6-to-7.md; on 7.x it opens references/upgrade-7-to-8.md. One reference file gets loaded, unless you are deliberately comparing versions.

From there it works through the renamed and dropped APIs: navigate, linking, themes, navigators, screen options. Peer-dependency and tooling bumps belong to the same pass. The policy is narrow — touch only the code the upgrade affects, and pick the simplest change that keeps behavior intact. The patterns inside the skill are starting points rather than a full catalogue, so an unfamiliar construct gets mapped onto the nearest example.

Verification comes after the edits. The package manager is read off package.json or the lockfile, then the project's type checker, linter and tests run where scripts exist. The “Automated checks” and “Manual checks” sections of the loaded reference are walked through as well, and any step that cannot run is reported with a reason. No such scripts in the repo means you verify by hand.

One brake is built in. When a navigator relies on APIs that neither the official docs nor the upgrade reference covers, the skill pauses and asks you before touching code. Same when the upgrade would need a guess about which behavior changes are acceptable.