expo-build-validation

Validates Expo app configuration, EAS profiles, and dependencies before release builds.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill expo-build-validation-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-build-validation
Source: https://github.com/gmackie/agent-skills/tree/main/skills/expo-build-validation
Command: npx skills add https://github.com/gmackie/agent-skills --skill expo-build-validation-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes references (resource) components.

What problem does it solve? Expo apps often fail late in the release cycle because of configuration drift, missing bundle identifiers, broken EAS profiles, or versioning mistakes that local development never surfaces. This Skill catches those technical readiness issues before TestFlight, Play testing, or store submission. ## Core Features & Use Cases - Config Surface Validation: Reviews app name, slug, version, iOS bundleIdentifier, Android package, build numbers, icons, splash, and permissions against a canonical checklist. - Dependency and SDK Health Checks: Runs npx expo install --check and npx expo doctor, flagging warnings that affect production builds. - EAS Profile and Environment Review: Verifies eas.json build and submit profiles, release environment variables, and expo-updates runtime policy. - Use Case: Before shipping a TestFlight build, run this Skill to confirm identifiers, assets, and release profiles are correct, then route behavior issues to Maestro QA or upload work to the submission skill. ## Quick Start Validate this Expo app before we ship a TestFlight build and report any blockers or major issues.

Frequently Asked Questions about expo-build-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an Expo app before a TestFlight build?▼

Validate an Expo app by inspecting app.json or app.config, eas.json, and asset files, then running npx expo install --check and npx expo doctor. Verify bundle identifiers, package names, and version codes before reporting blockers and routing to QA or submission.

What should I check in eas.json before a release build?▼

Check that eas.json contains build profiles for the intended target, a simulator or emulator profile if Maestro is used, and a submit profile when store upload is in scope. Also confirm release environment variables are available to the target profile.

Does this validation cover App Store review policy?▼

No, this validation covers technical readiness only, not App Store policy review. iOS review risk should be routed to a dedicated app-store-review skill, and product behavior issues belong in Maestro QA.

Why does my Expo release build fail even though local dev works?▼

A successful local dev run does not validate the release profile. Common causes include missing release environment variables, mismatched build numbers or version codes, broken EAS profiles, and dependency warnings that only affect production builds.

When should I not use Expo build validation?▼

Do not use it for product behavior testing or store-policy review, since it only checks technical readiness. Use Maestro QA for behavior verification and a submission skill for the actual upload execution.