What problem does it solve? Publishing Android builds to Google Play involves repetitive manual steps in the Play Console: uploading AAB files, configuring tracks, writing release notes, and managing staged rollouts. This Skill turns those steps into scripted gplay CLI workflows that can run locally or in CI/CD pipelines. ## Core Features & Use Cases - End-to-End Releases: Upload AAB/APK builds to internal, beta, or production tracks with a single gplay release command, including listings, screenshots, and multi-locale release notes. - Track Promotion & Staged Rollouts: Promote builds between tracks and control rollout fractions (10%, 50%, 100%) with update, halt, resume, and complete commands. - Safe Validation: Preview any release with --dry-run and follow a pre-release checklist covering version codes, signing, and permissions. - Use Case: An Android team wants to ship a new version: release to internal on week one, promote to beta on week two, then promote to production at 10% rollout and gradually increase to 100% over several days, all via terminal commands. ## Quick Start Ask the AI to release your signed app-release.aab to the Google Play internal track using the gplay CLI with your app's package name.
