rn-upgradelisted

Use to upgrade an existing Expo + RN project to a newer Expo SDK: bump `expo` and run `npx expo install --fix` to align every dependency, run `npx expo-doctor` for diagnostics, clear `node_modules`/`.expo`/Watchman caches, and native-rebuild (`expo prebuild --clean` + `pod install` + `gradlew clean`) only for bare-workflow projects — skip entirely for CNG (Continuous Native Generation) projects. Walks a breaking-changes checklist (removed APIs, moved imports, deprecated native modules like `expo-av` → `expo-audio` + `expo-video`) and supports beta/preview SDK upgrades via the `@next` tag. Reads `.workflow/meta.json` with `stack.framework="expo-rn"`; does NOT bump `phase` (this is a maintenance operation, not a pipeline step) but appends to `history`. Triggers on: "upgrade Expo SDK", "upgrade to Expo SDK 54", "bump expo version", "npx expo-doctor is failing", "upgrade React Native", "aggiorna Expo", "aggiorna il progetto RN", "expo install --fix". Not for: scaffolding a new app (`rn-bootstrap`), adding a new s
lukedj78/dev-flow · ★ 4 · Web & Frontend · score 77

Install: claude install-skill lukedj78/dev-flow

# rn-upgrade — upgrade an Expo + RN project to a newer SDK ## Contract See `references/contracts.md` (vendored from `dev-flow`). Key facts: - Reads `<project-root>/.workflow/meta.json#stack.framework` — must be `"expo-rn"`. - Requires `meta.json#phase ≥ "scaffolded"` (there must be a real app to upgrade — this skill never scaffolds). - This is a **maintenance** operation, not a pipeline step: it does **not** advance `phase`. It only appends a `history` entry recording the SDK versions before/after. - Idempotent in spirit: re-running on an already-upgraded project is a no-op after Step 1 detects `expo` is already at the target version (still worth running `expo-doctor` to catch drift). ## When this skill applies - Phase is `scaffolded` or later (an Expo app already exists at the project root). - User asks to move to a newer Expo SDK / React Native version, or reports `npx expo-doctor` failures, or dependency drift after manual `npm install`. - Orchestrator note: `dev-flow` does not route here automatically as part of the phase pipeline — this is invoked ad hoc, whenever the user wants to upgrade an already-running project. ## Knowledge dependencies (read these first) - `rn-fundamentals/SKILL.md` — the 4 non-negotiables (Expo managed, latest SDK, TypeScript, npm) this skill is restoring/advancing. - `rn-bootstrap/references/stack-defaults.md` — the pinned baseline versions used at scaffold time; the diff target for this upgrade. - `rn-eas-build-submit-update/references/ea