Repository inventory

callstackincubator/agent-skills

Skills indexed from this repository, with install-style signals scoped to the repo.
3 skills2.4K GitHub stars0 weekly installsGitHubOwner profile

Overview

This skill documents a practical React Native upgrade workflow that covers template diffs, dependency updates, Expo SDK considerations, and common pitfalls. It helps teams plan and execute upgrades with verification steps to reduce regressions and restore native config changes safely.

How this skill works

The skill uses a router-based approach to choose the right upgrade path and then inspects template diffs (via an Upgrade Helper-style comparison) to reconcile native code and config changes. It includes dependency compatibility checks, alignment guidance for React and React 19, optional Expo SDK steps, and a post-upgrade verification checklist to validate the app manually.

When to use it

  • When migrating a React Native app to a newer release
  • When reconciling native template changes after an automated upgrade
  • When triaging dependency compatibility and migration risk
  • When upgrading React to match React Native expectations (e.g., React 19)
  • When preparing Expo-managed apps for SDK upgrades

Best practices

  • Run template diffs and apply native config changes incrementally, not all at once
  • Lock and test transitive dependencies; prepare migration notes for breaking changes
  • Use a staged branch and CI gating for upgrade commits to catch regressions early
  • Follow Expo-specific steps only when the app is Expo-managed; separate those changes
  • Perform manual verification (builds, smoke tests, key user flows) before release

Example use cases

  • Upgrading a bare React Native app from 0.71 to 0.72 while preserving custom native modules
  • Aligning React package versions (including React 19) to satisfy new peer dependency rules
  • Upgrading an Expo-managed project to a new Expo SDK with conditional native changes
  • Running a dependency risk triage to decide which packages need immediate upgrades or replacements
  • Validating that critical screens and native integrations still work after template merges

FAQ

Not always, but you should inspect template diffs and apply required native config changes selectively—especially for Android and iOS manifests, gradle, and Podfile updates.

How do I handle transitive dependency breakages?

Run compatibility checks, pin versions in a temporary resolution, and either update or replace offending packages after testing in a staging branch.

3 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational