> upgrading-react-native
Upgrades 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.
curl "https://skillshub.wtf/callstackincubator/agent-skills/upgrading-react-native?format=md"Upgrading React Native
Overview
Covers the full React Native upgrade workflow: template diffs via Upgrade Helper, dependency updates, Expo SDK steps, and common pitfalls.
Typical Upgrade Sequence
- Route: Choose the right upgrade path via upgrading-react-native.md
- Diff: Fetch the canonical template diff using Upgrade Helper via upgrade-helper-core.md
- Dependencies: Assess and update third-party packages via upgrading-dependencies.md
- React: Align React version if upgraded via react.md
- Expo (if applicable): Apply Expo SDK layer via expo-sdk-upgrade.md
- Verify: Run post-upgrade checks via upgrade-verification.md
# Quick start: detect current version and fetch diff
npm pkg get dependencies.react-native --prefix "$APP_DIR"
npm view react-native dist-tags.latest
# Example: upgrading from 0.76.9 to 0.78.2
# 1. Fetch the template diff
curl -L -f -o /tmp/rn-diff.diff \
"https://raw.githubusercontent.com/react-native-community/rn-diff-purge/diffs/diffs/0.76.9..0.78.2.diff" \
&& echo "Diff downloaded OK" || echo "ERROR: diff not found, check versions"
# 2. Review changed files
grep -n "^diff --git" /tmp/rn-diff.diff
# 3. Update package.json, apply native changes, then install + rebuild
npm install --prefix "$APP_DIR"
cd "$APP_DIR/ios" && pod install
# 4. Validate: both platforms must build successfully
npx react-native build-android --mode debug --no-packager
xcodebuild -workspace "$APP_DIR/ios/App.xcworkspace" -scheme App -sdk iphonesimulator build
When to Apply
Reference these guidelines when:
- Moving a React Native app to a newer version
- Reconciling native config changes from Upgrade Helper
- Validating release notes for breaking changes
Quick Reference
| File | Description |
|---|---|
| upgrading-react-native.md | Router: choose the right upgrade path |
| upgrade-helper-core.md | Core Upgrade Helper workflow and reliability gates |
| upgrading-dependencies.md | Dependency compatibility checks and migration planning |
| react.md | React and React 19 upgrade alignment rules |
| expo-sdk-upgrade.md | Expo SDK-specific upgrade layer (conditional) |
| upgrade-verification.md | Manual post-upgrade verification checklist |
| monorepo-singlerepo-targeting.md | Monorepo and single-repo app targeting and command scoping |
Problem → Skill Mapping
| Problem | Start With |
|---|---|
| Need to upgrade React Native | upgrade-helper-core.md |
| Need dependency risk triage and migration options | upgrading-dependencies.md |
| Need React/React 19 package alignment | react.md |
| Need workflow routing first | upgrading-react-native.md |
| Need Expo SDK-specific steps | expo-sdk-upgrade.md |
| Need manual regression validation | upgrade-verification.md |
| Need repo/app command scoping | monorepo-singlerepo-targeting.md |
> related_skills --same-repo
> vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
> react-native-testing
Write tests using React Native Testing Library (RNTL) v13 and v14 (`@testing-library/react-native`). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React 18, sync render) and v14 (React 19+, async render). Triggers on: test files for React Native components, RNTL imports, mentions of "testing library", "write tests", "component tes
> dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", or "test this app" on mobile. Produces a structured report with reproducible evidence: screenshots, optional repro videos, and detailed steps for every issue.
> agent-device
Automates interactions for Apple-platform apps (iOS, tvOS, macOS) and Android devices. Use when navigating apps, taking snapshots/screenshots, tapping, typing, scrolling, or extracting UI info across mobile, TV, and desktop targets.