gpd-cli-usage
GPD CLI usage
Use this skill when you need to run or design gpd commands for Google Play Developer Console.
Command discovery
- Always use
--helpto confirm commands and flags.gpd --helpgpd publish --helpgpd monetization --help
Flag conventions
- Use explicit long flags (for example:
--package,--track,--status). - No interactive prompts; destructive operations require
--confirm. - Use
--allwhen the user wants all pages.
Output formats
- Default output is minified JSON.
- Use
--prettyfor readable JSON during debugging.
More from rudrankriyam/app-store-connect-cli-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.
2.3Kasc-xcode-build
Build, archive, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.
2.3Kasc-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.
2.2Kasc-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.
2.2Kasc-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.
2.2Kasc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
2.1K