Menu
Keep a repo's Revyl remote build mirrored with its CI pipeline - update both in the same PR and debug drift between them.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Revyl conventions for Cursor Cloud/background agents - headless VM rules, remote builds, artifact evidence, session cleanup, and PR flow.
MCP dev-first mobile loop for reliable screenshot-observe-action execution and grounded interactions.
Set up test-only auth bypass for Revyl runs across Expo, React Native, native iOS, native Android, and Flutter apps.
Generic CLI-first Revyl dev loop for hot reload, rebuild-loop, and device exploration.
Create robust Revyl E2E tests using CLI commands from app source analysis or exploratory sessions.
Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops.
| name | revyl-ci-sync |
| description | Keep a repo's Revyl remote build mirrored with its CI pipeline - update both in the same PR and debug drift between them. |
Use this skill when changing CI/build configuration in a repo that also has a Revyl remote build configured (.revyl/config.yaml with build.platforms or a remote dev loop in use).
Your Revyl remote build should mirror your CI pipeline. Both build the same app from the same source; when they diverge, "works on Revyl, fails in CI" (or the reverse) wastes a debugging session that a one-line sync would have prevented.
When a PR changes how CI builds the app — toolchain versions, build flags, env vars, dependency install steps, code signing, prebuild/codegen steps — mirror that change in the Revyl build configuration in the same PR. Not a follow-up.
Keep a small table in the repo (near the CI config or in the repo's agent docs) mapping each CI build step to its Revyl counterpart, for example:
| CI step | Revyl counterpart |
|---|---|
node 20.x setup | build.platforms.ios.command env / toolchain |
pod install --repo-update | same step in the Revyl build command |
EXPO_PUBLIC_* env vars | .revyl/config.yaml build env / launch vars |
The table's contents are repo-specific and live in the customer repo — this skill only prescribes the pattern: every row that changes on one side changes on both sides in the same PR.
When a build behaves differently on Revyl vs CI:
