Command workflow: /eas-deploy
Use this as a host-agnostic workflow. Adapt command names and capabilities to the active coding-agent host.
Workflow contract
yamldescription: "EAS Build + EAS Update + EAS Submit orchestration" argument-hint: "<context>"
/eas-deploy
Deploy via EAS. Choose: native build (binary change) or OTA update (JS-only change).
External action gate
This workflow may inspect a diff, prepare commands, and make a release plan locally. It must not run an EAS build or update, access an account, upload a binary, or change a rollout until the owner explicitly confirms the exact account, environment, channel, and action. A binary build and an OTA publication are separate confirmations.
Workflow
- Detect change type:
git difffor native files (ios/,android/,app.json, native modules inpackage.json). - If native change, use
eas-build-profilesto prepare the intendedeas buildcommand and list the signing, store, and cost implications. - If JS-only, use
eas-update-rolloutto prepare the intendedeas updatecommand, a rollback target, and a staged rollout proposal. - Ask the owner to confirm the precise external command before running it.
- For a native build, treat TestFlight or Play submission as a separate confirmed action; use the relevant submit skill only after the build is accepted.
- For an OTA update, agree on monitoring signals and a ramp schedule before each percentage increase.
- Output release notes, the prepared commands, rollout schedule, and every approval still needed.


