gpc-cli-usage
GPC CLI Usage
Use this skill when you need to run or design gpc commands for Google Play Console workflows.
Command discovery
Always confirm commands and flags before running:
gpc --help
gpc tracks --help
gpc bundles upload --help
Flag conventions
- Use explicit long flags:
--package,--track,--output. - No interactive prompts; destructive operations require
--confirm. - Short aliases:
-p(package),-o(output),-q(quiet).
Output formats
Default output is minified JSON. Available formats:
gpc apps list -o json # Default, machine-readable
gpc apps list -o table # Human-readable columns
gpc apps list -o yaml # YAML format
gpc apps list -o csv # CSV for spreadsheets
gpc apps list -o tsv # Tab-separated
gpc apps list -o minimal # Compact output
gpc apps list --pretty # Pretty-print JSON
Use --pretty for debugging. Use -o json (default) for automation and piping to jq.
Authentication
Configure a profile
gpc auth login --credentials /path/to/service-account.json --name myprofile --default-package com.example.app
Switch profiles
gpc auth list
gpc auth current
gpc auth switch --name otherprofile
Environment variables for CI
| Variable | Purpose |
|---|---|
GPC_CREDENTIALS_PATH |
Path to service account JSON |
GPC_CREDENTIALS_B64 |
Base64-encoded credentials |
GPC_PACKAGE |
Default package name |
GPC_PROFILE |
Default auth profile |
GPC_OUTPUT |
Default output format |
Diagnostics
gpc doctor # Check config, credentials, API access
gpc doctor --verbose # Detailed diagnostic output
Global flags
| Flag | Short | Description |
|---|---|---|
--package |
-p |
App package name (or GPC_PACKAGE) |
--output |
-o |
Output format (json, table, yaml, csv, tsv, minimal) |
--pretty |
Pretty-print JSON | |
--quiet |
-q |
Suppress non-essential output |
--debug |
Show API requests/responses | |
--dry-run |
Preview without applying changes | |
--timeout |
Request timeout (default 60s) | |
--profile |
Auth profile name |
Safety
- Use
--dry-runbefore destructive operations. - Use
--confirmflags explicitly; never pipeyesinto commands. - Check
gpc doctorbefore troubleshooting auth issues.
Agent behavior
- Always pass
--packageexplicitly unlessGPC_PACKAGEis confirmed set. - Prefer
--output jsonfor parsing; use--output tablewhen showing results to the user. - Run
gpc doctorfirst if auth errors occur.
More from androidpoet/playconsole-cli-skills
gpc-monetization
Manage in-app products, subscriptions, base plans, and subscription offers using gpc. Use when creating or updating monetization catalog.
12gpc-metadata-sync
Sync and manage Google Play store listings, images, and screenshots using gpc. Use when updating store metadata, uploading screenshots, or syncing from local directories.
12gpc-testing
Manage beta testing, internal test builds, tester groups, and internal app sharing using gpc. Use when setting up or managing testing workflows.
9gpc-release-flow
End-to-end release workflows for Google Play — upload bundles, manage tracks, staged rollouts, promotions, and halts. Use when uploading builds or managing releases.
9gpc-build-lifecycle
Manage Android app bundles, APKs, build processing, and debug symbol uploads using gpc. Use when uploading builds, checking build status, or uploading ProGuard mappings.
9gpc-device-management
Manage supported devices, device statistics, device tier configs, country availability, and reports using gpc. Use when working with device targeting or distribution settings.
9