Upgrade React Navigation to a new major version (6.x to 7.x or 7.x to 8.x), applying the required breaking changes — peer-dependency and tooling bumps, and renamed or removed navigate, linking, theme, navigator, and screen-option APIs — while preserving navigation behavior.
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
What it does
Upgrade React Navigation to a new major version (6.x to 7.x or 7.x to 8.x), applying the required breaking changes — peer-dependency and tooling bumps, and renamed or removed navigate, linking, theme, navigator, and screen-option APIs — while preserving navigation behavior.
When to use it
You are upgrading React Navigation major version (6.x -> 7.x or 7.x -> 8.x)
How agents load it
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Upgrade React Navigation; Goal; When to use; Adaptation policy; When to ask for clarification; References.
File analysis
File analysis: besides SKILL.md, the body references references/upgrade-6-to-7.md, references/upgrade-7-to-8.md. Those resources load on demand.
Upgrade React NavigationGoalWhen to useAdaptation policyWhen to ask for clarificationReferencesVerification
Upgrade React Navigation to a new major version (6.x to 7.x or 7.x to 8.x), applying the required breaking changes — peer-dependency and tooling bumps, and renamed or removed navigate, linking, theme, navigator, and screen-option APIs — while preserving navigation behavior.
DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 2
references/upgrade-6-to-7.md
references/upgrade-7-to-8.md
These paths are extracted from the text. Check the upstream package to verify the files exist.
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.
Ask your Agent to install
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "upgrade-react-navigation" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-08a2e03d54c46e94-Upgrade-React-Navigation.html
Save it as .cursor/skills/upgrade-react-navigation/SKILL.md or .claude/skills/upgrade-react-navigation/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/react-navigation/skills instead of creating only a SKILL.md.
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
Readable layout
name: upgrade-react-navigation
description: Upgrade React Navigation to a new major version (6.x to 7.x or 7.x to 8.x), applying the required breaking changes — peer-dependency and tooling bumps, and renamed or removed navigate, linking, theme, navigator, and screen-option APIs — while preserving navigation behavior.
Upgrade React Navigation
Goal
Upgrade React Navigation to the next major version and handle all required breaking changes while preserving existing navigation behavior.
When to use
You are upgrading React Navigation major version (6.x -> 7.x or 7.x -> 8.x).
Adaptation policy
Treat the patterns in this skill as canonical starting points, not an exhaustive list. The absence of an exact matching example is not a blocker.
Map local code to the closest pattern here and adapt it; infer an equivalent when the structure differs.
Prefer the simplest upgrade that preserves behavior.
Keep changes minimal and upgrade only the affected code.
When to ask for clarification
Inspect the local code first.
If, after reading the relevant navigator and the upgrade reference, you cannot determine with high confidence whether an API changed or how to update it, pause and ask the user before editing code.
Ask for clarification when:
A navigator uses APIs that are not covered in the official documentation or the upgrade reference.
The upgrade would require assumptions about which behavior changes are acceptable.
References
Check @react-navigation/native in package.json first.