メニュー
End-to-end release workflows for Google Play — upload bundles, manage tracks, staged rollouts, promotions, and halts. Use when uploading builds or managing releases.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create, deploy, and manage app recovery actions for Google Play using gpc. Use when responding to critical app issues that require user-facing recovery.
Manage Android app bundles, APKs, build processing, and debug symbol uploads using gpc. Use when uploading builds, checking build status, or uploading ProGuard mappings.
Guidance for using the Play Console CLI (gpc) — flags, output formats, auth profiles, pagination, and safety conventions. Use when asked to run or design gpc commands.
Manage supported devices, device statistics, device tier configs, country availability, and reports using gpc. Use when working with device targeting or distribution settings.
Sync and manage Google Play store listings, images, and screenshots using gpc. Use when updating store metadata, uploading screenshots, or syncing from local directories.
Manage in-app products, subscriptions, base plans, and subscription offers using gpc. Use when creating or updating monetization catalog.
| name | gpc-release-flow |
| description | End-to-end release workflows for Google Play — upload bundles, manage tracks, staged rollouts, promotions, and halts. Use when uploading builds or managing releases. |
Use this skill when you need to upload a build, publish to a track, promote between tracks, or manage rollouts.
gpc doctor passes).--package explicitly.gpc bundles upload --file app.aab --track internal --package com.example.app
gpc bundles upload --file app.aab --track beta \
--release-notes "Bug fixes and improvements" \
--release-notes-lang en-US \
--commit \
--package com.example.app
gpc bundles upload --file app.aab --track production \
--rollout 0.1 \
--package com.example.app
gpc tracks list --package com.example.app
gpc tracks get --track production --package com.example.app
gpc tracks update --track production \
--version-code 42 \
--status completed \
--rollout-percentage 1.0 \
--package com.example.app
gpc tracks promote --from internal --to beta --package com.example.app
gpc tracks promote --from beta --to production \
--rollout-percentage 0.05 \
--package com.example.app
gpc tracks update --track production --rollout-percentage 0.05 --package com.example.app
gpc tracks update --track production --rollout-percentage 0.20 --package com.example.app
gpc tracks update --track production --rollout-percentage 0.50 --package com.example.app
gpc tracks complete --track production --package com.example.app
gpc tracks halt --track production --package com.example.app
Use when you need precise control or multiple changes in one commit:
# 1. Create edit session
gpc edits create --package com.example.app
# 2. Make changes (upload, update tracks, etc.)
gpc bundles upload --file app.aab --package com.example.app
# 3. Validate before committing
gpc edits validate --edit-id $EDIT_ID --package com.example.app
# 4. Commit all changes atomically
gpc edits commit --edit-id $EDIT_ID --package com.example.app
gpc bundles wait --version-code 42 --timeout 600 --interval 30 --package com.example.app
--dry-run when available for production releases.gpc tracks get --track <track> output before and after changes.gpc tracks list to discover available tracks (internal, alpha, beta, production, custom).--release-notes-lang for locale-specific notes.--commit on upload auto-commits the edit; omit for manual edit lifecycle.