revyl

Plugin revyl in RevylAI/revyl-cli. Commands read from the repo's manifest — today.

Skills (17)

• revyl-build-ci-upload

  Add a Revyl upload step to the CI job that already builds the app (GitHub Actions, GitLab CI, Buildkite, or another runner) so each commit and pull request has a Revyl build tied to its exact commit, without building twice. Also covers uploading EAS or other hosted artifacts by URL and registering w

• revyl-build-config

  Write or fix the build recipes in a Revyl project's .revyl/config.yaml - build profiles per platform, simulator and emulator artifacts, framework recipes for native iOS, native Android, Expo, React Native, Flutter, and web, secrets for private dependencies, and caches. Use when setting up Revyl buil

• revyl-build

  Build this workspace's app on a Revyl cloud runner, or upload an artifact already built, and return the Revyl build ID, after one confirmation that it uses the organization's build minutes.

• revyl-ci-sync

  Keep a repo's Revyl remote build mirrored with its CI pipeline - update both in the same PR and debug drift between them.

• revyl-cli-auth-bypass

  Set up test-only auth bypass for Revyl runs across Web, Expo, React Native, native iOS, native Android, and Flutter apps.

• revyl-dev-loop

  Run, preview, debug, and verify mobile app changes on a real Revyl cloud device with the bundled, pinned Revyl CLI. Use after changing iOS, Android, Expo, React Native, Flutter, or other mobile app code and before reporting that work done, to offer an on-device check instead of leaving it to the pul

• revyl-device

  Start one Revyl cloud device (or browser) on a chosen app build and hand back the viewer link, after one confirmation that it uses the organization's device time.

• revyl-find-build

  Find which Revyl build to use for a commit, branch, pull request, or app - the exact-commit build from a pull-request preview or a CI upload, the build a run would pick by default, or a build's status and failure reason. Read-only and free. Use before testing or proving a change, or when asked wheth

• revyl-github

  Work with Revyl's GitHub integration - check whether the Revyl GitHub App is connected and can see this repository, connect it after the user agrees, configure pull-request builds and proof of changes in .revyl/config.yaml with their triggers, publish that configuration, wait for a pull request's pr

• revyl-headless

  Revyl conventions for unattended agent runs - Claude Code on the web, claude -p, codex exec, and CI jobs - covering CLI sign-in with REVYL_API_KEY, finding or making builds without Xcode, bounded waits, device evidence, and always stopping sessions. Use whenever this agent works with Revyl without a

• revyl-proof-automation

  Set up automatic device proof for every pull request - Revyl's own proof of changes on builds the Revyl GitHub App makes, the same proof on builds CI uploads, or a GitHub Actions job that runs claude -p or codex exec to prove the CI build. Use when asked to make CI or GitHub prove each pull request

• revyl-proof-ci

  Verify a mobile pull request using an exact-SHA match among its app's CI-uploaded Revyl builds, collect device evidence, and prepare a proof summary without rebuilding.

• revyl-proof

  Prove a pull request on a Revyl cloud device using the build of its exact head commit - the Revyl GitHub App's preview build or a CI upload - without rebuilding, and draft the proof for the pull request.

• revyl-setup

  Set up Revyl for this repository step by step - CLI sign-in, the hosted tools' sign-in, the project's .revyl/config.yaml and apps, and GitHub connection with pull-request builds - asking before every file write or account change.

• revyl-status

  Report Revyl readiness for this workspace without spending anything - pinned CLI, sign-in, project configuration, GitHub and pull-request builds, hosted tool connection, and running sessions or dev loops.

• revyl-stop

  Stop the Revyl device sessions, dev loops, and builds this conversation started, and nothing else.

• revyl-test

  Check the current change on a Revyl cloud device, build first - reuse the pull request's preview build or another build of this exact commit when one exists, otherwise build it after asking - then validate the changed behavior, report evidence, and stop everything it started.

Subagents (1)

• revyl-verifier

  Runs an authorized Revyl device check of a code change and returns only an evidence block. Use only when the conversation has explicit user authorization for a named app, platform, build, and device time - the revyl-test and revyl-proof skills hand work here with that authorization line.

MCP servers (1)

• revyl-workspace

  connects to: https://backend.revyl.ai/api/v1/mcp

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}"/hooks/revyl-session-check

• PostToolUse

  "${CLAUDE_PLUGIN_ROOT}"/hooks/revyl-offer-proof

Similar plugins