Doko-Demo-Doa/react-native-pdf-editor / .agents/skills/upgrading-react-native
upgrading-react-native
VerifiedUpgrades React Native apps to newer versions by applying rn-diff-purge template diffs, updating package.json dependencies, migrating native iOS and Android configuration, resolving CocoaPods and Gradle changes, and handling breaking API updates. Use when upgrading React Native, bumping RN version, updating from RN 0.x to 0.y, or migrating Expo SDK alongside a React Native upgrade.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.2 KB |
| agents/openai.yaml | config | 248 B |
| references/expo-sdk-upgrade.md | markdown | 2.5 KB |
| references/monorepo-singlerepo-targeting.md | markdown | 1.0 KB |
| references/react.md | markdown | 1.5 KB |
| references/upgrade-helper-core.md | markdown | 6.4 KB |
| references/upgrade-verification.md | markdown | 2.4 KB |
| references/upgrading-dependencies.md | markdown | 2.2 KB |
| references/upgrading-react-native.md | markdown | 2.7 KB |
references/react.md
View on GitHub---
title: React Upgrade Layer
impact: HIGH
tags: react, react-19, rntl, types
---
# Skill: React Upgrade Layer
React-specific upgrade rules to run when `react` changes during a React Native or Expo upgrade.
## When to Apply
- `react` version changes (major, minor, or patch).
- React Native target implies a newer React pairing.
- Tests/types break after React upgrade.
## React Pairing Rules
1. Keep companion packages aligned with installed React version:
- `react-test-renderer`
- `@types/react`
- `react-dom` (if used by the app)
2. Prefer matching React major and minor exactly; patch should also match when available.
3. Do not leave these packages on older `x.y` after upgrading `react`.
## React 19 Rules
1. Upgrade `@testing-library/react-native` to `v13+`.
2. Follow:
- [Expo React 19 Reference][expo-react-19-reference]
- [RNTL LLM Docs][rntl-llm-docs]
3. Expect type-level breakages from deprecated API removals; fix code and mocks accordingly.
## Related Skills
- [upgrade-helper-core.md](upgrade-helper-core.md) - Core RN upgrade workflow
- [upgrading-dependencies.md](upgrading-dependencies.md) - Dependency compatibility triage
- [expo-sdk-upgrade.md](expo-sdk-upgrade.md) - Expo-specific upgrade layer
- [upgrade-verification.md](upgrade-verification.md) - Post-upgrade validation, including agent-device-assisted checks
[expo-react-19-reference]: https://github.com/expo/skills/blob/main/plugins/upgrading-expo/skills/upgrading-expo/references/react-19.md
[rntl-llm-docs]: https://oss.callstack.com/react-native-testing-library/llms.txt
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |