play-developer-console

Name: play-developer-console
Author: rjyo

28stars4forks

How to install play-developer-console?

rjyo/moshi-skill/play-developer-console

$npx -y skills add rjyo/moshi-skill --skill play-developer-console

Installs into the current project.

Summary

Use when managing Google Play Developer Console metadata, graphics, tracks, app bundles, reviews, subscriptions, or in-app products with the local play CLI. Trigger this for Moshi Android Play Store work, especially when editing /Users/jyo/projects/ai/moshi/marketing/play ass

Files · 1

View on GitHub

SKILL.md

1	# Play Developer Console
2
3	Use the local Bun TypeScript CLI at:
4
5	```bash
6	/Users/jyo/projects/tools/play-cli
7	```
8
9	The CLI is linked locally with Bun and exposes:
10
11	```bash
12	play --help
13	```
14
15	For Moshi Android, run commands from:
16
17	```bash
18	/Users/jyo/projects/ai/moshi/marketing
19	```
20
21	The Play assets live in:
22
23	```bash
24	play/
25	.env
26	metadata/
27	images/
28	release-notes/
29	```
30
31	## Workflow
32
33	- Inspect `play/CLAUDE.md` and relevant local files before changing store assets.
34	- 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.
35	- Validate local listing text before upload:
36
37	```bash
38	play metadata validate
39	```
40
41	- Use read-only checks before and after changes:
42
43	```bash
44	play metadata list
45	play app-info show
46	play tracks list --json
47	play tracks show production --json
48	play reviews list --limit 5
49	```
50
51	## Release Workflow
52
53	Use the built-in track commands for release operations. Do not write ad hoc scripts against `src/api.ts` for normal release tasks.
54
55	Attach or update a release already uploaded to Play:
56
57	```bash
58	play tracks release internal \
59	--version-code 6 \
60	--status completed \
61	--name "Moshi 2.8.2" \
62	--notes en-US=play/release-notes/en-US.txt
63	```
64
65	Prepare a production draft with release notes:
66
67	```bash
68	play tracks release production \
69	--version-code 6 \
70	--status draft \
71	--name "Moshi 2.8.2" \
72	--notes en-US=play/release-notes/en-US.txt
73	```
74
75	If a draft app has stale releases that block validation, clear the track first, then create the intended release:
76
77	```bash
78	play tracks clear internal
79	play tracks release internal --version-code 6 --status draft --name "Moshi 2.8.2"
80	```
81
82	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.
83
84	- For bugs or missing Play API behavior, patch `/Users/jyo/projects/tools/play-cli`, then run:
85
86	```bash
87	cd /Users/jyo/projects/tools/play-cli
88	bun run typecheck
89	bun test
90	```
91
92	Retry from `/Users/jyo/projects/ai/moshi/marketing` after the fix.
93
94	## Auth
95
96	Moshi uses keyless local auth via `gcloud` ADC and a quota project in `play/.env`.
97	Do not create or require service account JSON keys unless the user explicitly asks.
98
99	Expected env keys:
100
101	```bash
102	PLAY_AUTH_MODE=gcloud
103	PLAY_QUOTA_PROJECT=play-cli-moshi-260429103059
104	PLAY_PACKAGE_NAME=app.getmoshi.android
105	```

People who liked this also viewed

6 picks

Type

play-developer-console

28stars4forks

View on GitHub

How to install play-developer-console?

rjyo/moshi-skill/play-developer-console

$npx -y skills add rjyo/moshi-skill --skill play-developer-console

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Play Developer Console
2
3	Use the local Bun TypeScript CLI at:
4
5	```bash
6	/Users/jyo/projects/tools/play-cli
7	```
8
9	The CLI is linked locally with Bun and exposes:
10
11	```bash
12	play --help
13	```
14
15	For Moshi Android, run commands from:
16
17	```bash
18	/Users/jyo/projects/ai/moshi/marketing
19	```
20
21	The Play assets live in:
22
23	```bash
24	play/
25	.env
26	metadata/
27	images/
28	release-notes/
29	```
30
31	## Workflow
32
33	- Inspect `play/CLAUDE.md` and relevant local files before changing store assets.
34	- 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.
35	- Validate local listing text before upload:
36
37	```bash
38	play metadata validate
39	```
40
41	- Use read-only checks before and after changes:
42
43	```bash
44	play metadata list
45	play app-info show
46	play tracks list --json
47	play tracks show production --json
48	play reviews list --limit 5
49	```
50
51	## Release Workflow
52
53	Use the built-in track commands for release operations. Do not write ad hoc scripts against `src/api.ts` for normal release tasks.
54
55	Attach or update a release already uploaded to Play:
56
57	```bash
58	play tracks release internal \
59	--version-code 6 \
60	--status completed \
61	--name "Moshi 2.8.2" \
62	--notes en-US=play/release-notes/en-US.txt
63	```
64
65	Prepare a production draft with release notes:
66
67	```bash
68	play tracks release production \
69	--version-code 6 \
70	--status draft \
71	--name "Moshi 2.8.2" \
72	--notes en-US=play/release-notes/en-US.txt
73	```
74
75	If a draft app has stale releases that block validation, clear the track first, then create the intended release:
76
77	```bash
78	play tracks clear internal
79	play tracks release internal --version-code 6 --status draft --name "Moshi 2.8.2"
80	```
81
82	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.
83
84	- For bugs or missing Play API behavior, patch `/Users/jyo/projects/tools/play-cli`, then run:
85
86	```bash
87	cd /Users/jyo/projects/tools/play-cli
88	bun run typecheck
89	bun test
90	```
91
92	Retry from `/Users/jyo/projects/ai/moshi/marketing` after the fix.
93
94	## Auth
95
96	Moshi uses keyless local auth via `gcloud` ADC and a quota project in `play/.env`.
97	Do not create or require service account JSON keys unless the user explicitly asks.
98
99	Expected env keys:
100
101	```bash
102	PLAY_AUTH_MODE=gcloud
103	PLAY_QUOTA_PROJECT=play-cli-moshi-260429103059
104	PLAY_PACKAGE_NAME=app.getmoshi.android
105	```

People who liked this also viewed

6 picks

Type