← ClaudeAtlas

gplay-cli-usagelisted

Conventions every gplay command shares: credential and package resolution, output formats, exit codes, `--dry-run`/`--confirm`/`GPLAY_READONLY` gates, the Edit lifecycle. Use when running any gplay command, wiring gplay into CI, branching on an exit code, or introspecting the Android Publisher API offline with `gplay schema`.
PollyGlot/google-play-cli-skills · ★ 5 · API & Backend · score 77
Install: claude install-skill PollyGlot/google-play-cli-skills
# gplay CLI conventions (foundation) Conventions shared by every gplay command; the normative source is [`docs/DESIGN.md`](https://github.com/PollyGlot/google-play-cli/blob/main/docs/DESIGN.md) in the CLI repo. `--help` wins over this skill when they disagree: ```bash gplay --help # the whole command tree gplay <group> --help # a namespace (releases, tracks, team, …) gplay <group> <command> --help # one command, with its real flags gplay exit-codes # the semantic exit-code table + diagnostic codes ``` ## Stability: the `[experimental]` banner gplay is GA. A command whose `--help` opens with `[experimental]` sits outside the Public contract (pin an exact release in CI, the banner says so); every other surface holds until a major bump, so CI can pin `v1` ([stability](https://gplay.sh/docs/concepts/stability/)). ## `gplay schema`: the offline API map Where `--help` documents gplay's own surface, `gplay schema <query>` introspects the Android Publisher API offline (no credential, no HTTP): methods, REST paths, types, enums. `[experimental]`; flags in `gplay schema --help`. ```bash gplay schema edits.tracks.update # a method's request/response, one hop deep gplay schema Track # a type's fields, types, enums gplay schema --command "releases upload" # the API methods a gplay command calls ``` ## Which credential Highest priority first: `--service-account <path-or-inline-JSON>`, `--account <name>