Use when validating an Expo app before internal release, TestFlight, Play testing, or store submission. Checks project config, EAS profiles, identifiers, assets, environment handling, and build-significant drift so the app is technically ready before QA handoff or submission.
Validate the build surface before you spend time on upload or review work.
This skill is for technical readiness, not Maestro QA and not store-policy review. Use it to find configuration drift, missing identifiers, bad asset setup, broken EAS profiles, or versioning mistakes before builds or submissions fail later.
Check for:
app.json or app.config.*package.jsoneas.jsonIdentify:
Review:
ios.bundleIdentifierandroid.packageUse references/release-validation-checklist.md as the canonical checklist.
Run the normal Expo health checks:
npx expo install --check
npx expo doctor
If the app is release-bound, flag dependency warnings that are likely to affect production builds instead of ignoring them as development noise.
Check:
eas.json exists and has the expected profilesexpo-updates is enabledDo not assume a successful local dev run means the release profile is valid.
Classify findings as:
Then route to the right next skill:
maestro-qa-report or maestro-qaapp-store-reviewexpo-build-submit| Need | Action |
|---|---|
| check config surface | inspect Expo config, assets, and eas.json |
| check dependency health | run npx expo install --check and npx expo doctor |
| check release profiles | review build and submit profiles in eas.json |
| decide next step | route into QA, review, or submit skill |
If the user asks:
validate this expo app before we ship a testflight build
do this:
eas.json