expo-cicd-workflows_skill

Overview

This skill helps developers understand, write, and validate EAS workflow YAML files for Expo projects. It guides creation of .eas/workflows/*.yml files, enforces schema-backed validation, and assists with triggers, jobs, expressions, and common CI/CD patterns. Use it to generate correct EAS pipelines and to diagnose workflow errors before committing changes.

How this skill works

The skill fetches the official EAS workflow JSON schema and documentation to determine valid job types, parameters, triggers, and expression contexts. It can generate or edit workflow YAML, check required fields, verify job dependencies, and run a schema-based validation script to report errors. It uses the schema as the source of truth so answers stay accurate as EAS evolves.

When to use it

• Creating a new EAS workflow in .eas/workflows/*.yml or .yaml
• Modifying job definitions, triggers, runners, or job parameters
• Validating workflows against the latest EAS schema before committing
• Debugging expression references like needs.*, jobs.*, or workflow.*
• Asking which job types, runner images, or trigger options are available

Best practices

• Always fetch the JSON schema before generating or validating workflows
• Keep workflows small and split complex pipelines into multiple jobs with clear needs/after relationships
• Use expression contexts (${ { } }) only for supported contexts defined in the schema
• Validate YAML with the provided validator script after every change
• Declare at least one trigger under on and verify concurrency and defaults when relevant

Example use cases

• Generate a workflow that builds iOS and Android binaries using pre-packaged build jobs and proper runner images
• Add a deployment job that runs after successful build jobs and consumes their outputs via needs
• Convert a GitHub Actions-style pipeline into an EAS workflow file with correct job types and parameters
• Validate existing workflow files and get a list of schema errors to fix
• Explain available trigger configurations (branch filters, workflow_dispatch inputs) based on the current schema