Skip to content

PollyGlot/google-play-cli-skills / skills/gplay-metadata-sync

gplay-metadata-sync

Verified

Store listing text and images as an on-disk tree synced with Play via `gplay metadata`. Use when editing a store listing or its screenshots, adding a locale, pulling the listing into version control, or gating a listing change in CI.

FileKindSize
SKILL.mdskill md4.2 KB
---
name: gplay-metadata-sync
description: Store listing text and images as an on-disk tree synced with Play via `gplay metadata`. Use when editing a store listing or its screenshots, adding a locale, pulling the listing into version control, or gating a listing change in CI.
---

# gplay metadata sync (listings + images)

Manage the store front: per-locale listing **text** and **images**, kept as an
on-disk tree and reconciled with Play. Shared conventions are in
`gplay-cli-usage`.

## The sync model

gplay treats a local `./metadata` tree as the desired state and reconciles it
with Play (ADR-0011). The loop:

```
pull  →  edit on disk  →  validate (offline)  →  apply --dry-run  →  apply --confirm
```

On disk, text is `<locale>/<field>.txt` (`title`, `short_description`,
`full_description`, `video`). Images sit under `<locale>/images/`: a singular
slot (`icon`, `featureGraphic`, `tvBanner`) is
`<type>.<ext>`; a gallery slot (the `*Screenshots` types) is
`<type>/1.<ext>…N.<ext>` in display order. Google retired `promoGraphic`:
a leftover `images/promoGraphic.*` (common in Fastlane `supply` trees) is
never uploaded, and `metadata images validate`/`images apply` warn with
its path, so delete the file.

- **`metadata pull`** copies the live Listings into the tree; additive, so
  `pull` then `apply` is a no-op.
- **`metadata validate`** lints the tree offline (no auth, no network); any
  violation exits `20`, so it fits a pre-commit hook or CI gate.
- **`metadata apply`** reconciles disk → Play, additive by default; `--prune`
  is the destructive opt-in (read `apply --help` before using it).
- **`metadata list`** summarizes what is live on Play, per locale.

## Apply safely

```bash
gplay metadata pull --dir ./metadata
# …edit the .txt files…
gplay metadata validate --dir ./metadata          # offline lint, exit 20 on error
gplay metadata apply --dir ./metadata --dry-run    # ONLINE diff, prints per-locale delta
gplay metadata apply --dir ./metadata --confirm    # publishes, live immediately
```

`apply --dry-run --output json` is the diff schema
`{package, changes[], summary}`, so a CI gate is
`jq -e '.summary.create + .summary.update > 0'`. The real `apply` is
`--confirm`-gated and atomic: one Edit, any locale failure publishes nothing.

### The tree stays inside the repo

Every file gplay reads or writes under `--dir` must resolve inside the repo
once symlinks are followed: a `title.txt` symlinked to a file outside the
tree, or a pre-placed link where `pull` will write, is refused. Locale names
are checked in BCP 47 (`en-US`, not `en_US`) before an Edit opens. Monorepos
that share translations or assets through symlinks can set
`GPLAY_ALLOW_EXTERNAL_SYMLINKS=1`: symlink egress is then followed, one `NOTE`
per outbound path on stderr, while a `..` escape and any path derived from API
data (a locale Play returns, a package name) stay contained regardless.

## Images

```bash
gplay metadata images list --package com.example.app
gplay metadata images list --type icon                    # one image type, all locales
gplay metadata images pull --dir ./metadata
gplay metadata images validate --dir ./metadata           # offline lint, exit 20 on error
gplay metadata images apply --dir ./metadata --dry-run    # ONLINE per-slot delta
gplay metadata images apply --dir ./metadata --confirm    # publishes, live immediately
```

`metadata images` follows the same loop for per-locale image slots (ADR-0013):

- `images list` walks the 9 slot types across every locale; `--type` narrows
  to one.
- `images pull` downloads each image at original size (gplay 2.4.2+; older
  builds pulled 512px thumbnails, so re-pull before an `apply` round trip),
  checks it against the API's `sha256`, and writes the tree all or nothing: a
  failed or mismatched download leaves the destination untouched.
- `images apply` is additive like the text side; `--prune` deletes online-only
  images (destructive, `--confirm`); `--locale`/`--type` scope the run.
  `--ai-generated` (`[experimental]`) attests the uploaded images are AI
  generated, `--ai-generated=false` that they are not; unset sends nothing.
- The CI gate is `jq -e '.summary.upload + .summary.delete + .summary.reorder
  > 0'` over `apply --dry-run --output json` (`{package, slots[], summary}`).
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall