mcpField
E
expo-cicd-workflows

expo-cicd-workflows

github.com/expoCloud & DevOps3.5k39.2k installsUpdated today
Repository

About expo-cicd-workflows

A skill for writing and editing EAS CI/CD workflow YAML files. It fetches the current workflow schema and documentation, then validates files against the schema.

Key features

  1. 01Write and edit workflow YAML
  2. 02Fetch current JSON schema and docs
  3. 03Check job parameters and references
  4. 04Review expression contexts and conditions
  5. 05Validate workflows against the schema

Use cases

  1. 01Create an EAS CI/CD workflow
  2. 02Update a workflow using the current schema
  3. 03Check job dependencies and expressions
  4. 04Validate workflow YAML structure

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/expo/skills --skill expo-cicd-workflows

After installing, type/expo-cicd-workflowsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
scripts/
fetch.js
package.json
validate.js

Details

From the project README

EAS Workflows Skill

Help developers write and edit EAS CI/CD workflow YAML files.

Reference Documentation

Fetch these resources before generating or validating workflow files. First resolve this skill's directory, then use the fetch script in its scripts/ directory. It is implemented using Node.js and caches responses using ETags for efficiency:

# Fetch resources
node <skill-dir>/scripts/fetch.js <url>

  1. JSON Schema — https://api.expo.dev/v2/workflows/schema

    • It is NECESSARY to fetch this schema
    • Source of truth for validation
    • All job types and their required/optional parameters
    • Trigger types and configurations
    • Runner types, VM images, and all enums

  2. Syntax Documentation — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/syntax.mdx

    • Overview of workflow YAML syntax
    • Examples and English explanations
    • Expression syntax and contexts

  3. Pre-packaged Jobs — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/pre-packaged-jobs.mdx

    • Documentation for supported pre-packaged job types
    • Job-specific parameters and outputs

Do not rely on memorized values; these resources evolve as new features are added.

Workflow File Location

Workflows live in .eas/workflows/*.yml (or .yaml).

Top-Level Structure

A workflow file has these top-level keys:

  • name — Display name for the workflow
  • on — Triggers that start the workflow (at least one required)
  • jobs — Job definitions (required)
  • defaults — Shared defaults for all jobs
  • concurrency — Control parallel workflow runs

Consult the schema for the full specification of each section.

Expressions

Use ${{ }} syntax for dynamic values. The schema defines available contexts:

  • github.* — GitHub repository and event information
  • inputs.* — Values from workflow_dispatch inputs
  • needs.* — Outputs and status from dependent jobs
  • jobs.* — Job outputs (alternative syntax)
  • steps.* — Step outputs within custom jobs
  • workflow.* — Workflow metadata

Generating Workflows

When generating or editing workflows:

  1. Fetch the schema to get current job types, parameters, and allowed values
  2. Validate that required fields are present for each job type
  3. Verify job references in needs and after exist in the workflow
  4. Check that expressions reference valid contexts and outputs
  5. Ensure if conditions respect the schema's length constraints

Validation

After generating or editing a workflow file, validate it against the schema:

# Install dependencies if missing
[ -d "<skill-dir>/scripts/node_modules" ] || npm install --prefix <skill-dir>/scripts

node <skill-dir>/scripts/validate.js <workflow.yml> [workflow2.yml ...]

The validator fetches the latest schema and checks the YAML structure. Fix any reported errors before considering the workflow complete.

Answering Questions

When users ask about available options (job types, triggers, runner types, etc.), fetch the schema and derive the answer from it rather than relying on potentially outdated information.

Comments

Markdown supported