agentleFS
Sign inStart free
mybigdaymybigday/whisper.rn/.agents/skills/upgrade-react-native/SKILL.md

upgrade-react-native

Skill809 starsChanged 8 months agoMITView on GitHub

Upgrade React Native version in example/ directory using rn-diff-purge methodology. Use when the user wants to upgrade react-native, migrate to a new RN version, or update React Native dependencies in the example app. Handles diff retrieval, systematic file changes, dependency updates, and conflict resolution.

  • Installs packages

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 1

    1. mybigday/llama.rn★ 1.1k100% same

    Edited · 0

    None found.

    Wrote their own version · 5

    1. Shopify/flash-list★ 7.2ksame name
    2. callstack/repack★ 1.9ksame name
    3. react-native-community/skills★ 27same name
    4. Phaedra-Solutions/cursor-rules★ 4same name
    5. ltatarev/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Actually apply all changes: - do not just list them in a summary

    line 12
  2. Very specific:

    Read example/package.json to identify the current react-native version.

    line 18
  3. Distinctive:

    If diff returns 404: version combination may not exist in rn-diff-purge.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Upgrade React Native

CRITICAL: File Editing Rules

  • ALWAYS use Edit/Write tools to make changes - never just report what should be changed
  • VERIFY changes were saved by reading the file after editing
  • Actually apply all changes - do not just list them in a summary

Workflow

1. Detect Current Version

Read example/package.json to identify the current react-native version.

2. Fetch Upgrade Diff

curl -s "https://raw.githubusercontent.com/react-native-community/rn-diff-purge/diffs/diffs/{currentVersion}..{toVersion}.diff" | awk '/^GIT binary patch$/,/^diff --git/ {if (/^diff --git/) print; next} 1'

For binary files (e.g., gradle-wrapper.jar):

https://raw.githubusercontent.com/react-native-community/rn-diff-purge/release/{version}/RnDiffApp/android/gradle/wrapper/gradle-wrapper.jar

If diff returns 404: version combination may not exist in rn-diff-purge; suggest alternative paths or manual migration.

3. Analyze Diff

Identify file additions/deletions/modifications, dependency changes, config updates, native code changes (iOS + Android), and breaking changes.

4. Apply Changes Systematically

Order: package.json deps -> config files -> code changes -> iOS native -> Android native. Preserve custom modifications in example/.

5. Update Related Packages

  • react - Check: npm view react-native@{version} peerDependencies.react
  • react-test-renderer - Must match React version
  • @react-native-community/cli - Check compatibility with RN version

6. Install Dependencies

cd example && npm install

For iOS:

cd example/ios && pod install

7. Validate

Rebuild native apps from root directory:

npm run build:ios
npm run build:android

Guidelines

  • Incremental upgrades: For multiple major versions, upgrade incrementally (e.g., 0.72 -> 0.73 -> 0.74).
  • Conflict resolution: Preserve custom functionality, explain conflicts, recommend safest resolution.
  • Never delete custom code without explicit confirmation.
  • Only work within example/ unless explicitly instructed otherwise.
  • Document all changes: Summarize modified/added/deleted files, breaking changes, and manual steps needed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free