gpc-cli-usage（GPC CLI 使用）

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

Diagnostics

gpc doctor              # Check config, credentials, API access
gpc doctor --verbose    # Detailed diagnostic output

Global flags

Safety

• Use --dry-run before destructive operations.
• Use --confirm flags explicitly; never pipe yes into commands.
• Check gpc doctor before troubleshooting auth issues.

Agent behavior

• Always pass --package explicitly unless GPC_PACKAGE is confirmed set.
• Prefer --output json for parsing; use --output table when showing results to the user.
• Run gpc doctor first if auth errors occur.