Generate and Validate EAS CI/CD Workflows

Helps write and edit EAS CI/CD workflow YAML files (.eas/workflows/*.yml) by fetching live reference documentation rather than relying on memorized syntax: the JSON Schema at api.expo.dev/v2/workflows/schema (source of truth for job types, triggers, runners, and enums), the workflow syntax docs, and the pre-packaged-jobs docs, all fetched via a caching Node.js script that uses ETags. It documents the top-level workflow structure - name (a display name), on (the triggers that start a run, at least one required), jobs (the required job definitions), defaults (settings shared across all jobs), and concurrency (controlling parallel runs of the same workflow) - and the ${{ }} expression syntax with its available contexts (github.*, inputs.*, needs.*, jobs.*, steps.*, workflow.*).

node {baseDir}/scripts/fetch.js <url>

When generating or editing a workflow, it fetches the schema first, validates required fields per job type, verifies that needs/after job references actually exist in the workflow, checks that expressions reference valid contexts and outputs, and confirms if conditions respect the schema's length constraints - then runs a validator script against the live schema before considering the file complete. The validator auto-installs its own Node dependencies if missing before running, so a first-time validation doesn't require a separate setup step.

Use it when creating, editing, or validating .eas/workflows/*.yml files for an Expo project, or answering questions about EAS build pipelines, deployment automation, triggers, or CI/CD configuration - always by fetching the current schema rather than trusting potentially outdated memorized syntax.

Input: a new or existing EAS workflow YAML file, or a question about available job types, triggers, or runners. Output: a schema-validated workflow file, or a schema-derived answer to a configuration question, plus validator error output to fix before the file is considered complete.

Fetches directly from Expo's own schema and documentation endpoints (api.expo.dev/v2/workflows/schema, the expo/expo GitHub repo's workflow syntax and pre-packaged-jobs docs) via a caching fetch script, and validates through a companion scripts/validate.js. The same live-fetch discipline applies to answering questions - if a user asks what job types, triggers, or runner types are available, it fetches the schema and derives the answer from it rather than trusting a memorized list that may already be stale.

Expo developers writing or maintaining EAS CI/CD workflows who want schema-accurate YAML rather than guessing at syntax from memory, working from workflow files that live at .eas/workflows/*.yml or .yaml.