eas-workflows

What problem does it solve? Writing EAS Workflows YAML files for Expo CI/CD requires up-to-date knowledge of job types, triggers, and expression syntax that changes frequently, and mistakes are only caught late without proper validation. ## Core Features & Use Cases - Schema-driven authoring: Fetches the live JSON schema from api.expo.dev plus official syntax and pre-packaged jobs documentation before generating or editing workflow files. - CLI validation: Validates each workflow file with eas-cli workflow:validate, which checks build profile references against eas.json and runs EAS server-side checks. - Cached fetching: Uses a Node.js fetch script with ETag and Cache-Control based HTTP caching to avoid redundant downloads of reference documentation. - Use Case: You want a workflow that builds your app on every push to main and submits to the stores on demand; the skill generates .eas/workflows/deploy.yml with correct triggers, job dependencies via needs, and ${{ }} expressions, then validates it. ## Quick Start Ask the assistant to create an EAS workflow file that builds your Expo app on every push to main and validate it with the EAS CLI.