gpd-id-resolver
GPD ID Resolver
Use this skill to map names to IDs needed by other gpd commands.
Package name (app ID)
- Package name is the primary identifier:
com.example.app. - Always pass
--packageexplicitly for deterministic results.
Track names
- Common tracks:
internal,alpha,beta,production. - List tracks:
gpd publish tracks --package com.example.app
Version codes and release status
- Use release status to find version codes on a track:
gpd publish status --package com.example.app --track production
Tester groups
- List testers by track:
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-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.
31gpd-release-flow
End-to-end release workflows for Google Play using gpd publish commands, tracks, rollouts, and edit lifecycle. Use when uploading builds or managing releases.
31