OTA Update Deployment with EAS

VerifiedSafe

Deploys JavaScript/UI changes (components, styling, business logic) via EAS Update without native rebuild. Use when referring to 'OTA', 'EAS Update', or 'JS update' to quickly push code changes.

Sby Skills Guide Bot
DevelopmentIntermediate
406/2/2026
Claude Code
#ota#eas-update#deployment#react-native#expo

Recommended for

Our review

Deploys JavaScript/UI changes via EAS Update without requiring a native rebuild (OTA).

Strengths

  • Enables fast updates without native rebuild
  • Targets UI, business logic, and JS dependency changes
  • Uses dev branch by default for safe deployment
  • Non-interactive for automated workflows

Limitations

  • Only works for pure JavaScript changes
  • Does not replace native rebuild for native modules or configuration
  • Requires internet connection and an configured EAS project
When to use it

Use this skill to quickly deploy UI or logic changes without waiting for a native rebuild.

When not to use it

Do not use for native changes like permissions, icons, or native modules; prefer a full rebuild instead.

Security analysis

Safe
Quality score92/100

The skill runs a well-known Expo CLI command ('npx eas update') with a fixed branch and message. No destructive, exfiltrating, or obfuscated actions. It operates within the app directory and does not involve sensitive data exposure or system compromise.

No concerns found

Examples

Deploy UI fix
Deploy the updated login screen styles via OTA.
Quick business logic update
Run an OTA update for the new API call changes.
EAS Update for branch dev
Use EAS Update to deploy my latest JS changes without rebuilding.

name: ota description: Deploy JavaScript/UI changes via EAS Update without native rebuild (OTA = Over-The-Air). Use for UI components, styling, screen layouts, navigation, business logic, API calls, text/strings, or pure JS dependencies. Use when the user mentions "ota", "EAS Update", "OTA deploy", "JS update", "UI update", or wants to deploy code changes without rebuilding. user-invocable: true

/ota - OTA Update Deployment

Run EAS Update to deploy JavaScript/UI changes without native rebuild (OTA = Over-The-Air).

Execution Requirements

IMPORTANT: Execute npx commands from the app root directory (APPNAME directory, not the .git root).

Command

cd APPNAME  # Move to app directory from project root
npx eas update --branch dev --message "OTA update from Claude Code" --non-interactive

Use This For

JavaScript-only changes that don't require native rebuild:

  • UI components, styling
  • Screen layouts, navigation
  • Business logic (TypeScript/JavaScript)
  • API calls, text/strings
  • Pure JS dependencies

When NOT to Use

For native changes, use /dist-dev-client instead:

  • Intent handlers / deep links
  • Permissions
  • Native modules
  • Package name changes
  • App icon or splash screen
  • Build configuration (app.json affecting native)

Instructions for Claude

When this skill is invoked:

  1. Verify current directory: Ensure you're in the app root (APPNAME directory)
  2. Run EAS Update:
    cd APPNAME
    npx eas update --branch dev --message "OTA update from Claude Code" --non-interactive
    
  3. Inform the user: Explain that the update was deployed and users need to restart the app to see changes
  4. Verify success: Check command output for successful deployment confirmation

Success Indicators

  • "Published" message in output
  • Update ID shown
  • No error messages

Common Issues

  • Not in app directory: Remind user that command must be run from APPNAME directory
  • Not logged in: Run eas login first
  • No EAS project: Run eas init first
Related skills