rn-eas-deploylisted

Use to deploy an Expo + RN app end-to-end: initialize eas.json with 3 profiles (development/preview/production), set up credentials (APNs key, Android keystore) via `eas credentials`, build for preview to smoke-test, build production, submit to App Store Connect + Play Console via EAS Submit, configure EAS Update channels (preview + production), and verify the post-submission checklist from rn-publishing-payments. Reads .workflow/meta.json with stack.framework="expo-rn" and phase="feature_complete". Sets phase to "deployed" on success. Triggers on: "deploy to production", "ship to App Store / Play Store", "release the app". Not for: granular EAS Build/Submit/Update operations (rn-eas-build-submit-update), store metadata work (rn-publishing-payments).
lukedj78/dev-flow · ★ 4 · Web & Frontend · score 77

Install: claude install-skill lukedj78/dev-flow

# rn-eas-deploy — end-to-end EAS deploy orchestration ## Contract See `references/contracts.md`. Key facts: - Reads `<project-root>/.workflow/meta.json#stack.framework` — must be `"expo-rn"`. - Requires `meta.json#phase ≥ "feature_complete"`. - Wires `eas.json` + credentials + first production build + submit. - Sets `meta.json#stack.deploy = "eas"` and `phase = "deployed"` on success. - Idempotent: re-running detects existing config and skips already-done steps. ## When this skill applies - Phase is `feature_complete` (or later, for subsequent releases). - User says: "deploy", "ship to stores", "release". - Orchestrator routes here from `dev-flow`. ## Knowledge dependencies (read these first) - `rn-eas-build-submit-update/SKILL.md` — the underlying knowledge (eas.json, credentials, channels, runtimeVersion). - `rn-eas-build-submit-update/references/eas-json.md` �� canonical 3-profile shape. - `rn-eas-build-submit-update/references/credentials.md` — how `eas credentials` works. - `rn-publishing-payments/references/review-guidelines.md` — pre-submission checklist. - `rn-publishing-payments/references/store-assets.md` — what assets must be ready. - `references/observability.md` — EAS Observe (production performance) + EAS Update Insights (OTA rollout health): what to enable before Step 7, what to read after Step 8/9, and how to turn the numbers into a hotfix/rollback decision. ## Workflow ### Step 1 — Verify preconditions Read `.workflow/meta.json`. Abort if: - `stack.