Agent skill

Gplay Release Flow

End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands.

MITAuto-check passedDevelopment

Install Gplay Release Flow

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-release-flow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/android-dev/gplay-release-flow .claude/skills/gplay-release-flow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "gplay-release-flow" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-release-flow into .claude/skills/gplay-release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-release-flow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-release-flow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-release-flow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/android-dev/gplay-release-flow .agents/skills/gplay-release-flow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gplay-release-flow" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-release-flow into .agents/skills/gplay-release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-release-flow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-release-flow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/android-dev/gplay-release-flow .cursor/skills/gplay-release-flow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gplay-release-flow" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-release-flow into .cursor/skills/gplay-release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-release-flow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/hanamizuki/solopreneur.git --path skills/android-dev/gplay-release-flow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-release-flow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/android-dev/gplay-release-flow .gemini/skills/gplay-release-flow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gplay-release-flow" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-release-flow into .gemini/skills/gplay-release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-release-flow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-release-flow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/android-dev/gplay-release-flow .github/skills/gplay-release-flow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gplay-release-flow" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-release-flow into .github/skills/gplay-release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-release-flow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-release-flow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/android-dev/gplay-release-flow .opencode/skills/gplay-release-flow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gplay-release-flow" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-release-flow into .opencode/skills/gplay-release-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-release-flow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gplay-release-flow
GitHub stars: 152
Token cost: ~2.1k tokens
SKILL.md length: 468 words
Files: 2
Skills in repo: 31
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands.

Works in 5 steps: Create edit session → Upload bundle → Update track → …
Asked to upload a build
SKILL.md covers Preconditions, Android Release, Track Promotion and Staged Rollout Management, plus 5 more sections
Calls jq

What it does

Gplay Release Flow is an agent skill from hanamizuki/solopreneur. End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands. Use when asked to upload a build, distribute to testers, or release to production.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_VENDOR.md`).

It sits in Development, covering Changelog and release notes and End-to-end testing. It works with Android. The repository describes itself as: Skills and agents for solopreneurs — ship, review, debug, and think through problems with AI. The licence is MIT.

When your agent uses it

Asked to upload a build
Distribute to testers
Release to production

Example prompts

“/gplay-release-flow”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Create edit session
Upload bundle
Update track
Validate edit
Commit edit (publishes changes)

What it can do on your machine

Read from SKILL.md and the folder at commit f43f001. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gplay Release Flow loads about 2.1k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 468 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~59
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hanamizuki/solopreneur at commit f43f001, republished under its MIT licence (© hanamizuki). 468 words, ~2,136 tokens.

Download SKILL.mdSave it as .claude/skills/gplay-release-flow/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: gplay-release-flow
description: End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands. Use when asked to upload a build, distribute to testers, or release to production.

Release flow (Internal, Beta, Production)

Use this skill when you need to get a new build onto Google Play Store.

Preconditions

Ensure credentials are set (gplay auth login or GPLAY_SERVICE_ACCOUNT env var).
Build must be an AAB (App Bundle) or APK.
Version code must be higher than previous releases.
Service account needs "Release Manager" permission in Play Console.

Android Release

Preferred end-to-end commands

Internal track (for internal testing):

bash

gplay release \
  --package com.example.app \
  --track internal \
  --bundle app-release.aab

Beta track (for beta testers):

bash

gplay release \
  --package com.example.app \
  --track beta \
  --bundle app-release.aab \
  --release-notes @release-notes.json

Production with staged rollout (gradual release):

bash

gplay release \
  --package com.example.app \
  --track production \
  --bundle app-release.aab \
  --release-notes @release-notes.json \
  --rollout 0.1

Dry run (preview the release without executing):

bash

gplay release \
  --package com.example.app \
  --track production \
  --bundle app-release.aab \
  --dry-run

Release with metadata (listings and screenshots)

Include store listings from a directory:

bash

gplay release \
  --package com.example.app \
  --track production \
  --bundle app-release.aab \
  --listings-dir ./metadata \
  --screenshots-dir ./metadata

Skip metadata or screenshots:

bash

# Upload bundle only, skip metadata sync
gplay release \
  --package com.example.app \
  --track production \
  --bundle app-release.aab \
  --skip-metadata

# Upload bundle and metadata, skip screenshots
gplay release \
  --package com.example.app \
  --track production \
  --bundle app-release.aab \
  --listings-dir ./metadata \
  --skip-screenshots

Combine listings and screenshots directories:

bash

gplay release \
  --package com.example.app \
  --track beta \
  --bundle app-release.aab \
  --listings-dir ./metadata/listings \
  --screenshots-dir ./metadata/images \
  --release-notes @release-notes.json

Manual sequence (when you need more control)

Create edit session:

bash

EDIT_ID=$(gplay edits create --package com.example.app | jq -r '.id')

Upload bundle:

bash

gplay bundles upload \
  --package com.example.app \
  --edit $EDIT_ID \
  --file app-release.aab

Update track:

bash

gplay tracks update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track production \
  --releases @releases.json

--releases takes a JSON array of track releases (or @file).

Validate edit:

bash

gplay edits validate --package com.example.app --edit $EDIT_ID

Commit edit (publishes changes):

bash

gplay edits commit --package com.example.app --edit $EDIT_ID

Track Promotion

Promote a release from one track to another:

bash

# Promote from internal to beta
gplay promote \
  --package com.example.app \
  --from internal \
  --to beta

# Promote from beta to production with 25% rollout
gplay promote \
  --package com.example.app \
  --from beta \
  --to production \
  --rollout 0.25

Staged Rollout Management

Start with a 10% rollout (fraction 0.1):

bash

gplay release \
  --package com.example.app \
  --track production \
  --bundle app.aab \
  --rollout 0.1

Increase to 50% (fraction 0.5):

bash

gplay rollout update \
  --package com.example.app \
  --track production \
  --rollout 0.5

Halt rollout (pause distribution):

bash

gplay rollout halt --package com.example.app --track production

Resume rollout:

bash

gplay rollout resume --package com.example.app --track production

Complete rollout (release to 100%):

bash

gplay rollout complete --package com.example.app --track production

Release Notes Format

The single --release-notes flag accepts three shapes: a JSON array (multi-locale), plain text (auto-assigned to en-US), or an @file path pointing to either. There is no separate locale flag.

JSON array format (multi-locale)

release-notes.json — a JSON array of {language, text} entries:

json

[
  { "language": "en-US", "text": "Bug fixes and performance improvements" },
  { "language": "es-ES", "text": "Correcciones de errores y mejoras de rendimiento" },
  { "language": "fr-FR", "text": "Corrections de bugs et améliorations des performances" }
]

Pass it with --release-notes @release-notes.json.

Plain text format (single locale)

Provide release notes as plain text — it is auto-assigned to en-US:

bash

gplay release \
  --package com.example.app \
  --track beta \
  --bundle app.aab \
  --release-notes "Bug fixes and performance improvements"

Or from a file (plain text or a JSON array) with @:

bash

gplay release \
  --package com.example.app \
  --track beta \
  --bundle app.aab \
  --release-notes @release-notes.txt

Show full SKILL.md (214 more words)Show less

Release Flags Reference

Flag	Description
`--package`	App package name (required)
`--track`	Target track (production, beta, alpha, internal; default: `internal`)
`--bundle`	Path to AAB file (use `--bundle` or `--apk`, not both)
`--apk`	Path to APK file (alternative to `--bundle`)
`--release-notes`	Release notes: plain text (auto-assigned en-US), a JSON array of `{language, text}`, or `@file`
`--rollout`	Staged rollout fraction (0.0-1.0, default: 1.0 for full rollout)
`--listings-dir`	Directory containing store listings to sync
`--screenshots-dir`	Directory containing screenshots to upload
`--skip-metadata`	Skip metadata/listings sync during release
`--skip-screenshots`	Skip screenshots upload during release
`--dry-run`	Preview the release without executing
`--output`	Output format (`json`, `table`, `markdown`)

Pre-release Checklist

Before releasing, verify:

Version code is incremented
AAB/APK is signed with correct keystore
ProGuard/R8 mapping files uploaded (for crash reports)
Release notes written for all locales
Testing completed on internal/beta track
Service account has correct permissions
Dry run passes: gplay release ... --dry-run

Common Release Strategies

Strategy 1: Internal -> Beta -> Production

bash

# Week 1: Internal
gplay release --package com.example.app --track internal --bundle app.aab

# Week 2: Beta (after testing)
gplay promote --package com.example.app --from internal --to beta

# Week 3: Production with staged rollout
gplay promote --package com.example.app --from beta --to production --rollout 0.1
gplay rollout update --package com.example.app --track production --rollout 0.5  # Day 2
gplay rollout complete --package com.example.app --track production             # Day 7

Strategy 2: Direct to Production with Staged Rollout

bash

# Day 1: 10%
gplay release --package com.example.app --track production --bundle app.aab --rollout 0.1

# Day 2: 25%
gplay rollout update --package com.example.app --track production --rollout 0.25

# Day 3: 50%
gplay rollout update --package com.example.app --track production --rollout 0.5

# Day 7: 100%
gplay rollout complete --package com.example.app --track production

Strategy 3: Full release with metadata and dry-run verification

bash

# 1. Dry run to verify everything
gplay release \
  --package com.example.app \
  --track production \
  --bundle app.aab \
  --listings-dir ./metadata \
  --screenshots-dir ./metadata \
  --release-notes @release-notes.json \
  --rollout 0.1 \
  --dry-run

# 2. Execute the release
gplay release \
  --package com.example.app \
  --track production \
  --bundle app.aab \
  --listings-dir ./metadata \
  --screenshots-dir ./metadata \
  --release-notes @release-notes.json \
  --rollout 0.1

Notes

Always use --help to verify flags for the exact command.
Use --output table for human-readable output; default is JSON.
For CI/CD, use GPLAY_SERVICE_ACCOUNT environment variable.
Upload deobfuscation files after each release for crash symbolication.
Use --dry-run in CI to validate releases before actual deployment.

Files

SKILL.md and 1 other file in skills/android-dev/gplay-release-flow of hanamizuki/solopreneur.

SKILL.md
_VENDOR.md

Open the folder on GitHubat commit f43f001

Compare with similar skills

Gplay Release Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gplay Release Flow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gplay Release Flow this skillhanamizuki/solopreneur	152	—	~2.1k	Automated safety check: Pass	MIT	14 days ago
Debugging Litert GPU Accuracygoogle-ai-edge/LiteRT	3.5k	—	~3.3k	Automated safety check: Pass	Apache-2.0	today
Release Changelogsk2andy/candy-browser	532	—	~593	Automated safety check: Pass	MPL-2.0	2 days ago
Update Version CatalogRedMadRobot/gradle-version-catalogs	118	—	~9.5k	Automated safety check: Pass	MIT	8 days ago
Bump Versionarindamxd/camerax-android	132	—	~603	Automated safety check: Pass	Apache-2.0	9 days ago
Commitmanhpham90vn/Deskhub	133	—	~978	Automated safety check: Pass	MIT	today

Similar skills

Debugging Litert GPU Accuracy
google-ai-edge/LiteRT
Diagnoses and fixes on-device GPU numerical corruption, garbage generation, zeroed KV caches, and ML Drift delegate lowering bugs for LiteRT and LiteRT-LM models on Android (OpenCL and WebGPU).
3.5k GitHub stars~3.3k tokensUpdated today
DevelopmentAuto-check passed
Release Changelog
sk2andy/candy-browser
Create or update Candy Browser's English, image-rich, versioned release notes for the in-app What's New presentation and the matching GitHub release.
532 GitHub stars~593 tokensUpdated 2 days ago
DevelopmentAuto-check passed
Update Version Catalog
RedMadRobot/gradle-version-catalogs
Use EVERY time the user asks to update / bump the version catalogs, "сделать обновление", "обновить каталог(и)", "обнови версии", "оформи изменения", "update the catalog", or to record dependency…
118 GitHub stars~9.5k tokensUpdated 8 days ago
DevelopmentAuto-check passed
Bump Version
arindamxd/camerax-android
Increments versionCodeOffset for another Play upload of the same versionName, updates RELEASE.md shipping numbers, and prints Play Console release notes from git log since the previous upload.
132 GitHub stars~603 tokensUpdated 9 days ago
DevelopmentAuto-check passed
Commit
manhpham90vn/Deskhub
Write a Deskhub commit message. An agent skill from manhpham90vn/Deskhub.
133 GitHub stars~978 tokensUpdated today
DevelopmentAuto-check passed
Version Update Workflow
HkingAuditore/civ-game
Summarize and execute civ-game version update workflow, including change classification, changelog entry authoring, release highlights, and verification steps.
113 GitHub stars~742 tokensUpdated 18 days ago
DevelopmentAuto-check passed

Questions about Gplay Release Flow

What does Gplay Release Flow do?

End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands. Gplay Release Flow is an agent skill from hanamizuki/solopreneur. End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands.

When should I use Gplay Release Flow?

Gplay Release Flow fits situations like: asked to upload a build; distribute to testers; release to production.

How do I install Gplay Release Flow in Claude Code?

Run `npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a claude-code`. Or copy the skill folder (skills/android-dev/gplay-release-flow in hanamizuki/solopreneur) into .claude/skills/gplay-release-flow in your project. Claude Code loads it when a task matches its description.

How do I install Gplay Release Flow in Codex?

Run `npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a codex`. Or copy the skill folder (skills/android-dev/gplay-release-flow in hanamizuki/solopreneur) into .agents/skills/gplay-release-flow in your project. Codex loads it when a task matches its description.

Can I use Gplay Release Flow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hanamizuki/solopreneur --skill gplay-release-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gplay-release-flow, .gemini/skills/gplay-release-flow, .github/skills/gplay-release-flow and .opencode/skills/gplay-release-flow in your project.

What does Gplay Release Flow need to run?

Going by SKILL.md and its folder, Gplay Release Flow needs the command-line tools its instructions call (jq).

Does Gplay Release Flow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gplay Release Flow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gplay Release Flow use?

Gplay Release Flow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gplay Release Flow use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gplay Release Flow?

Skills that share tags, products or a category with Gplay Release Flow: Debugging Litert GPU Accuracy (google-ai-edge/LiteRT, 3.5k stars), Release Changelog (sk2andy/candy-browser, 532 stars), Update Version Catalog (RedMadRobot/gradle-version-catalogs, 118 stars) and Bump Version (arindamxd/camerax-android, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gplay Release Flow?

hanamizuki (a GitHub user) maintains it in hanamizuki/solopreneur, which has 152 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on September 26, 2026.

Source: hanamizuki/solopreneur on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gplay Release Flow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Release flow (Internal, Beta, Production)

Preconditions

Android Release

Preferred end-to-end commands

Release with metadata (listings and screenshots)

Manual sequence (when you need more control)

Track Promotion

Staged Rollout Management

Release Notes Format

JSON array format (multi-locale)

Plain text format (single locale)

Release Flags Reference

Pre-release Checklist

Common Release Strategies

Notes

Files

Compare with similar skills

Similar skills

More from hanamizuki/solopreneur

Related

Questions about Gplay Release Flow