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/upgrade-verification.md
View on GitHub---
title: Upgrade Verification
impact: HIGH
tags: verification, regression, android, ios, navigation
---
# Skill: Upgrade Verification
Manual and agent-assisted validation checklist after React Native and/or Expo upgrades.
## Scope
- Focus on behavior and UX regressions that static diffs cannot prove.
- Keep checks small, repeatable, and tied to critical user flows.
## Agent-Assisted Checks
Use `agent-device` for runnable app verification. If it is missing and device verification is needed, install it through the environment's approved/trusted path or ask the user to install or enable it.
1. If the agent environment exposes an `agent-device` skill, read it before planning exact commands.
2. If the `agent-device` CLI is available, follow its `agent-device help workflow` guidance.
3. Open or install the upgraded app, drive each critical scenario, and verify with UI snapshots.
4. Capture screenshots, logs, and pass/fail evidence for changed flows.
5. Fall back to human validation for credentials, physical-device-only hardware, or profiler surfaces the agent cannot inspect.
## Behavior Checks (Required)
1. App launch and core journeys work on both iOS and Android.
2. Navigation behavior is correct (forward/back stack, params, deep links, modal flows).
3. Android edge-to-edge is visually correct (status bar, nav bar, safe area insets, keyboard overlays).
4. Permissions and device APIs work (camera, location, notifications, file/media access).
5. Background/restore paths work (app resume, push open, interrupted flows).
## Build and Test Gates
1. Run unit/integration tests and fix all upgrade-related failures.
2. If `target_version >= 0.81` and tests fail due to missing modules, add proper mocks.
- Example (`BackHandler` mock removal): https://github.com/facebook/react-native/issues/52667#issuecomment-3094788618
3. Build installable artifacts for both platforms.
4. For Expo apps, run `npx expo-doctor` from [expo-sdk-upgrade.md](expo-sdk-upgrade.md).
## Evidence to Capture
- Screen recordings/screenshots for changed flows.
- List of verified scenarios and pass/fail status.
- Follow-up fixes for any observed regressions.
## Related Skills
- [upgrading-react-native.md](upgrading-react-native.md) - Upgrade workflow router
- [upgrade-helper-core.md](upgrade-helper-core.md) - Core RN diff/merge workflow
- [expo-sdk-upgrade.md](expo-sdk-upgrade.md) - Expo-specific checks and commands
- [react.md](react.md) - React-specific upgrade rules
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 |