# Build Expo CI/CD Workflows

Expo teams need current EAS workflow YAML that matches the live schema. This skill helps Claude, Codex, and Claude Code fetch references, draft workflows, and validate changes before use.

## Install

```bash
npx skillstore add expo/expo-cicd-workflows
```

## Metadata

- Status: approved
- Slug: expo-expo-cicd-workflows
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: ee4b54b45f1bedbf8284934ebad7ba55a30845a9fd0363c12eaa8dbf9e4b211c
- Author: expo
- GitHub username: expo
- License: MIT License
- Repository: https://github.com/expo/skills/tree/main/plugins/expo-deployment/skills/expo-cicd-workflows/
- Ref: 0519034dad657fb1f7706e0550e962beeda73fdf
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 75
- Public page: https://skillstore.pages.dev/skills/expo-expo-cicd-workflows
- Manifest: https://skillstore.pages.dev/api/skills/expo-expo-cicd-workflows/manifest

## Capabilities

- Fetches the latest EAS workflow schema and Expo documentation references.
- Creates and edits workflow YAML under .eas/workflows paths.
- Validates workflow YAML files against the official Expo schema.
- Explains workflow keys such as triggers, jobs, defaults, and concurrency.
- Checks job references, dependencies, and expression contexts during edits.

## Use Cases

- Create a release workflow: Draft a workflow that builds and submits an Expo app with schema-valid settings.
- Validate deployment automation: Check existing EAS workflow files before merging release automation changes.
- Standardize CI/CD templates: Create reusable workflow patterns for multiple Expo projects and teams.

## Prompt Templates

### Create a Basic Workflow

```
Create an EAS workflow for my Expo app that runs on manual trigger and builds Android and iOS.
```

### Validate an Existing Workflow

```
Review .eas/workflows/release.yml, fetch the current Expo schema, and tell me what must change before it is valid.
```

### Add Release Conditions

```
Update my EAS workflow so production submission only runs for the main branch or a manual production input.
```

### Design a Multi-Job Pipeline

```
Design an EAS workflow with separate preview build, production build, and submit jobs. Validate dependencies and expression contexts.
```

## Limitations

- Requires network access to fetch current Expo schema and documentation.
- Does not deploy apps or run EAS builds by itself.
- Depends on local Node tooling for the included validation script.
- Cannot guarantee current enum values without fetching the latest references.

## Best Practices

- Fetch the latest schema before creating or changing workflow files.
- Validate every modified workflow before treating it as complete.
- Keep job dependencies and expression contexts explicit and easy to review.

## Anti Patterns

- Relying on memorized job types or enum values.
- Writing workflow YAML without running schema validation.
- Referencing outputs, contexts, or jobs that are not defined.

## Security Audit

- Audited at: 2026-07-09T12:29:05.698\+00:00
- Summary: No prompt injection or secret exfiltration intent was found in the reviewed files. Most external-command findings are false positives from JavaScript template literals, Markdown fences, or inline code. The skill has intentional outbound network access for Expo references and should keep that access constrained.

## Stats

- Views: 164
- Downloads: 7
- Favorites: 0
- Popularity score: 0