mcpField
P
play-developer-console

play-developer-console

github.com/rjyoDevelopment30666 installsUpdated 13w ago
Repository

About play-developer-console

play-developer-console guides use of a local Bun TypeScript CLI to manage Moshi Android's Google Play listings and releases. It covers metadata validation, app and review checks, and track operations, with read-only inspection before edits.

Key features

  1. 01Inspect listing metadata and app information
  2. 02Validate local listing text
  3. 03Check reviews and release tracks
  4. 04Create or update track releases
  5. 05Use local gcloud ADC authentication

Use cases

  1. 01Inspect existing configuration before editing store assets
  2. 02Validate listing text before upload
  3. 03Review production track and recent reviews
  4. 04Prepare internal or production releases

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rjyo/moshi-skill --skill play-developer-console

After installing, type/play-developer-consolein Claude Code to confirm it loaded.

Details

From the project README

Play Developer Console

Use the local Bun TypeScript CLI at:

/Users/jyo/projects/tools/play-cli

The CLI is linked locally with Bun and exposes:

play --help

For Moshi Android, run commands from:

/Users/jyo/projects/ai/moshi/marketing

The Play assets live in:

play/
  .env
  metadata/
  images/
  release-notes/

Workflow

  • Inspect play/CLAUDE.md and relevant local files before changing store assets.
  • Run one Play edit-backed command at a time. Do not parallelize play metadata, play app-info, play images, play bundle, or play tracks commands.
  • Validate local listing text before upload:
play metadata validate
  • Use read-only checks before and after changes:
play metadata list
play app-info show
play tracks list --json
play tracks show production --json
play reviews list --limit 5

Release Workflow

Use the built-in track commands for release operations. Do not write ad hoc scripts against src/api.ts for normal release tasks.

Attach or update a release already uploaded to Play:

play tracks release internal \
  --version-code 6 \
  --status completed \
  --name "Moshi 2.8.2" \
  --notes en-US=play/release-notes/en-US.txt

Prepare a production draft with release notes:

play tracks release production \
  --version-code 6 \
  --status draft \
  --name "Moshi 2.8.2" \
  --notes en-US=play/release-notes/en-US.txt

If a draft app has stale releases that block validation, clear the track first, then create the intended release:

play tracks clear internal
play tracks release internal --version-code 6 --status draft --name "Moshi 2.8.2"

When no --notes flag is provided, play tracks release reads all files in play/release-notes/ as localized release notes. Use --no-notes only when intentionally omitting notes.

  • For bugs or missing Play API behavior, patch /Users/jyo/projects/tools/play-cli, then run:
cd /Users/jyo/projects/tools/play-cli
bun run typecheck
bun test

Retry from /Users/jyo/projects/ai/moshi/marketing after the fix.

Auth

Moshi uses keyless local auth via gcloud ADC and a quota project in play/.env. Do not create or require service account JSON keys unless the user explicitly asks.

Expected env keys:

PLAY_AUTH_MODE=gcloud
PLAY_QUOTA_PROJECT=play-cli-moshi-260429103059
PLAY_PACKAGE_NAME=app.getmoshi.android

Comments

Markdown supported