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/asc-skills
asc-cli-usage
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
758asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
710asc-id-resolver
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
691asc-release-flow
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
690asc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
684asc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
675