expo-cicd-workflows
GitHub协助开发者编写和编辑 Expo EAS CI/CD 工作流 YAML 文件。通过动态获取最新 JSON Schema 和文档，确保生成符合规范的工作流配置，并提供自动化验证功能以检查语法、必填字段及依赖引用，保障构建流水线正确性。
Trigger Scenarios
Install
npx skills add fanfan-de/anybox --skill expo-cicd-workflows -g -y
SKILL.md
Frontmatter
{
"name": "expo-cicd-workflows",
"license": "MIT License",
"version": "1.0.0",
"description": "Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI\/CD or workflows in an Expo or EAS context, mentions .eas\/workflows\/, or wants help with EAS build pipelines or deployment automation.",
"allowed-tools": "Read,Write,Bash(node:*)"
}
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>
-
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
-
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
-
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 workflowon— Triggers that start the workflow (at least one required)jobs— Job definitions (required)defaults— Shared defaults for all jobsconcurrency— 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 informationinputs.*— Values fromworkflow_dispatchinputsneeds.*— Outputs and status from dependent jobsjobs.*— Job outputs (alternative syntax)steps.*— Step outputs within custom jobsworkflow.*— Workflow metadata
Generating Workflows
When generating or editing workflows:
- Fetch the schema to get current job types, parameters, and allowed values
- Validate that required fields are present for each job type
- Verify job references in
needsandafterexist in the workflow - Check that expressions reference valid contexts and outputs
- Ensure
ifconditions 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.
Version History
- 08dc189 Current 2026-07-05 18:57
