Menu
Promote a release from Google Play internal testing to a closed testing track (Alpha or App Hive Testing). Use when the user asks to promote a release, move to closed testing, push to alpha, push to App Hive Testing, or mentions track promotion.
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
Planner-Generator-Evaluator harness for large, multi-screen features or major refactors. Separates planning, implementation, and evaluation into distinct phases with isolated context, preventing self-grading bias and context drift. Use when the user asks to build a large feature, do a major refactor, or implement something spanning multiple screens/files.
Unified release for both Android and iOS from a single version tag. Runs quality gates, bumps both platform versions in one commit, tags, builds both platforms, uploads Android to Play Store, and opens iOS archive for App Store upload. Use when the user asks to release, ship, cut a release, or make a new version.
Build and upload an Android release based on an existing git tag. Runs lint and all tests first (unit and instrumented), bumps version to match the tag, builds release AAB and APK (without debug info), commits the version bump, and uploads the AAB to Google Play Store internal testing. Use when the user asks to make an Android release, build for Play Store, or upload to Google Play.
Create a GitHub release with a version tag and auto-generated release notes. Does not build artifacts or upload to any store. Use when the user asks to tag a version, create a GitHub release, cut a release, or prepare release notes.
Build an iOS release based on an existing git tag. Bumps version to match the tag, builds the shared KMP framework and the iOS app archive. Use when the user asks to make an iOS release, build for App Store, or create an iOS archive.
Add translated strings and plurals to Android and iOS locale files. Use when adding new user-facing strings or plurals, fixing MissingTranslation lint errors, or when the user asks to translate, localize, or add strings to all languages.
| name | play-store-promote |
| description | Promote a release from Google Play internal testing to a closed testing track (Alpha or App Hive Testing). Use when the user asks to promote a release, move to closed testing, push to alpha, push to App Hive Testing, or mentions track promotion. |
Promote a release from the internal testing track to one of the closed testing tracks using the Gradle Play Publisher (GPP) plugin.
app/play-service-account.jsonAsk the user which closed testing track to promote to:
| Track | Name in Play Console |
|---|---|
| Alpha | Alpha |
| App Hive Testing | App Hive Testing |
Promote to Alpha:
./gradlew promoteReleaseArtifact --from-track internal --promote-track alpha --release-status completed
Promote to App Hive Testing:
./gradlew promoteReleaseArtifact --from-track internal --promote-track "App Hive Testing" --release-status completed
block_until_ms: 60000 (promotion typically takes 10-30s).--from-track internal flag tells GPP to take the latest release from internal testing.--release-status completed flag makes the release immediately available to testers.After a successful promotion, provide:
| Task | Command |
|---|---|
| Promote to Alpha | ./gradlew promoteReleaseArtifact --from-track internal --promote-track alpha --release-status completed |
| Promote to App Hive Testing | ./gradlew promoteReleaseArtifact --from-track internal --promote-track "App Hive Testing" --release-status completed |
| Promote to production | ./gradlew promoteReleaseArtifact --from-track internal --promote-track production --release-status completed |
| Staged rollout to production | ./gradlew promoteReleaseArtifact --from-track internal --promote-track production --release-status inProgress --user-fraction 0.1 |
./gradlew publishReleaseBundle.