gpd-submission-health
GPD Submission Health
Use this skill to reduce Play Console submission failures and validate readiness.
Preconditions
- Auth configured and package name resolved.
- Build uploaded and available for the target track.
- Store listing metadata and assets updated.
Pre-submission checklist
1. Validate edit (if using edit lifecycle)
gpd publish edit validate EDIT_ID --package com.example.app
2. Confirm release status
gpd publish status --package com.example.app --track production
More from rudrankriyam/gpd-cli-skills
gpd-cli
Manage Google Play Developer Console using the gpd CLI. Use when working with Android app publishing, Play Store releases, app reviews, Android vitals, in-app purchases, subscriptions, or when the user mentions Google Play, Play Store, Android publishing, or gpd.
35gpd-cli-usage
Guidance for using the Google Play Developer CLI (flags, output formats, auth, pagination). Use when asked to run or design gpd commands for Play Console workflows.
34gpd-metadata-sync
Sync and validate Google Play metadata, listings, and assets with gpd, including Fastlane-style workflows. Use when updating store listings or translations.
32gpd-betagroups
Orchestrate Google Play beta testing groups and distribution using gpd. Use when managing testers, internal testing, or beta rollouts.
31gpd-id-resolver
Resolve Google Play identifiers (package, tracks, version codes, products, subscriptions) using gpd. Use when commands require IDs or exact values.
31gpd-ppp-pricing
Set region-specific pricing for Google Play subscriptions and products using gpd monetization commands. Use when adjusting prices by territory or PPP strategy.
31