Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From Harness Mobile
EAS Build / Submit / Update conventions for Expo apps — development/preview/production profiles in eas.json, the OTA-vs-binary decision via expo prebuild --check, and two-key gating on eas submit. Use when configuring EAS profiles or running EAS Build/Submit/Update for a React Native Expo project.
npx claudepluginhub camilool8/harness-engineering-templates --plugin harness-mobileHow this skill is triggered — by the user, by Claude, or both
Slash command
/harness-mobile:addon-eas-buildThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- `development` — dev client; internal distribution; for live-reload + native debugging.
Runs automated patient safety test suites for healthcare deployments, blocking on CRITICAL failures in CDSS accuracy, PHI exposure, and data integrity.
Share bugs, ideas, or general feedback.
eas.json)development — dev client; internal distribution; for live-reload + native debugging.preview — internal QA build; internal distribution; tester groups can install via QR.production — store-bound build; store distribution; binary or OTA via EAS Update.Run npx expo prebuild --check before deciding:
eas update --branch production (OTA, no review needed).eas build --profile production then eas submit --profile production (requires App Store / Play Store review).The eas-release-coordinator agent refuses eas submit without safety.two_key=true or a typed token in autonomous loops.