Agent skill

Gplay Rollout Management

by hanamizuki in hanamizuki/solopreneur

Staged rollout orchestration and monitoring for Google Play releases.

MITAuto-check passedDevOps & Cloud

Install Gplay Rollout Management

skills CLI
$ npx skills add hanamizuki/solopreneur --skill gplay-rollout-management -a claude-code

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

GitHub CLI
$ gh skill install hanamizuki/solopreneur gplay-rollout-management --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-rollout-management .claude/skills/gplay-rollout-management && 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/

Facts

Skill name
gplay-rollout-management
GitHub stars
152
Token cost
~1.6k tokens
SKILL.md length
334 words
Files
2
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Staged rollout orchestration and monitoring for Google Play releases.

  • Works in 7 steps: Always start with <20% - Catch issues… → Monitor for 24 hours between increases → Have a hotfix plan - Be ready to fix… → …
  • Implementing gradual release strategies
  • SKILL.md covers What is Staged Rollout?, Start a Staged Rollout, Increase Rollout Percentage and Halt Rollout, plus 11 more sections
  • Calls jq

What it does

Gplay Rollout Management is an agent skill from hanamizuki/solopreneur. Staged rollout orchestration and monitoring for Google Play releases. Use when implementing gradual release strategies.

Its SKILL.md is about 1.6k 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 DevOps & Cloud. 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

  • Implementing gradual release strategies

Example prompts

  • “/gplay-rollout-management”

Workflow steps

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

  1. Always start with <20% - Catch issues early
  2. Monitor for 24 hours between increases
  3. Have a hotfix plan - Be ready to fix critical bugs quickly
  4. Set up alerts - Monitor crash rates automatically
  5. Test thoroughly in beta - Reduce production issues
  6. Communicate with users - Update release notes
  7. Don't rush - Gradual rollout is for safety

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 Rollout Management loads about 1.6k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 334 words of instructions outside code blocks.

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

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). 334 words, ~1,594 tokens.

Download SKILL.mdSave it as .claude/skills/gplay-rollout-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gplay-rollout-management
description
Staged rollout orchestration and monitoring for Google Play releases. Use when implementing gradual release strategies.

Staged Rollout Management

Use this skill when you need to manage gradual releases on Google Play.

What is Staged Rollout?

Staged rollout releases your app to a percentage of users, allowing you to:

  • Monitor crash rates and reviews before full release
  • Catch critical bugs with limited user impact
  • Gradually increase distribution as confidence grows

Start a Staged Rollout

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

This releases to 10% of users.

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

Increase Rollout Percentage

bash
# Increase to 25%
gplay rollout update \
  --package com.example.app \
  --track production \
  --rollout 0.25

# Increase to 50%
gplay rollout update \
  --package com.example.app \
  --track production \
  --rollout 0.5

# Increase to 100% (or use complete)
gplay rollout update \
  --package com.example.app \
  --track production \
  --rollout 1.0

Halt Rollout

Pause distribution if issues are detected:

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

Effect:

  • Stops further distribution
  • Existing users keep the update
  • New users don't receive the update

Resume Rollout

Resume after fixing issues:

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

Complete Rollout

Release to 100% of users:

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

Check Rollout Status

bash
gplay tracks get \
  --package com.example.app \
  --track production \
  | jq '.releases[0].userFraction'
Conservative (7-day rollout)
bash
# Day 1: 10%
gplay release --package com.example.app --track production --bundle app.aab --rollout 0.1

# Day 2: 25% (monitor crash rate)
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 5: 75%
gplay rollout update --package com.example.app --track production --rollout 0.75

# Day 7: 100%
gplay rollout complete --package com.example.app --track production
Aggressive (3-day rollout)
bash
# Day 1: 25%
gplay release --package com.example.app --track production --bundle app.aab --rollout 0.25

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

# Day 3: 100%
gplay rollout complete --package com.example.app --track production
Cautious (for critical apps)
bash
# Day 1: 5%
gplay release --package com.example.app --track production --bundle app.aab --rollout 0.05

# Day 2: 10% (monitor carefully)
gplay rollout update --package com.example.app --track production --rollout 0.1

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

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

# Day 7: 75%
gplay rollout update --package com.example.app --track production --rollout 0.75

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

Monitoring During Rollout

Check crash rate

Use Play Console → Quality → Android vitals

Monitor reviews
bash
# Get recent reviews
gplay reviews list \
  --package com.example.app \
  --paginate \
  | jq '.reviews[] | select(.createdTime > "2025-02-05") | {rating, text: .comments[0].userComment.text}'
Filter 1-star reviews
bash
gplay reviews list \
  --package com.example.app \
  | jq '.reviews[] | select(.rating == 1) | .comments[0].userComment.text'

Decision Matrix

MetricAction
Crash rate < 1%Continue rollout
Crash rate 1-2%Halt, investigate
Crash rate > 2%Halt, rollback if possible
1-star reviews spikeHalt, investigate
ANR rate spikeHalt, investigate
No issues after 24hIncrease rollout

Rollback Strategy

Google Play doesn't support automatic rollback, but you can:

Option 1: Upload hotfix
bash
# Build hotfix with higher version code
./gradlew bundleRelease

# Release hotfix immediately to 100%
gplay release \
  --package com.example.app \
  --track production \
  --bundle app-hotfix.aab
Option 2: Promote previous version

This requires the previous version still be in beta track:

bash
gplay promote \
  --package com.example.app \
  --from beta \
  --to production

Best Practices

  1. Always start with <20% - Catch issues early
  2. Monitor for 24 hours between increases
  3. Have a hotfix plan - Be ready to fix critical bugs quickly
  4. Set up alerts - Monitor crash rates automatically
  5. Test thoroughly in beta - Reduce production issues
  6. Communicate with users - Update release notes
  7. Don't rush - Gradual rollout is for safety

Common Mistakes to Avoid

❌ Don't:

  • Jump from 10% to 100% immediately
  • Ignore crash rate increases
  • Roll out during weekends/holidays (slower monitoring)
  • Skip beta testing phase

✅ Do:

  • Monitor crash rates constantly
  • Have team available during rollout
  • Prepare hotfix in advance
  • Communicate expected timeline to stakeholders

Automation Example

CI/CD with automated rollout
yaml
# .github/workflows/rollout.yml
name: Automated Rollout

on:
  schedule:
    - cron: '0 9 * * *'  # Daily at 9 AM

jobs:
  increase-rollout:
    runs-on: ubuntu-latest
    steps:
      - name: Get current rollout
        id: current
        run: |
          CURRENT=$(gplay tracks get --package $PACKAGE | jq -r '.releases[0].userFraction')
          echo "fraction=$CURRENT" >> $GITHUB_OUTPUT

      - name: Increase rollout
        if: steps.current.outputs.fraction < 1.0
        run: |
          NEW_FRACTION=$(echo "${{ steps.current.outputs.fraction }} + 0.25" | bc)
          gplay rollout update --package $PACKAGE --track production --rollout $NEW_FRACTION

Support

For manual rollout control, always use the Google Play Console UI as a backup.

© hanamizuki, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

  • SKILL.md
  • _VENDOR.md

Open the folder on GitHubat commit f43f001

Compare with similar skills

Gplay Rollout Management 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 Rollout Management compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gplay Rollout Management this skillhanamizuki/solopreneur152—~1.6kAutomated safety check: PassMIT
Gradle Build PerformanceMoustachauve/WLED-Android1693 repos~2kAutomated safety check: PassApache-2.0
GitHub Workflowsamirisback/automated-build-android-app-with-github-action346—~550Automated safety check: PassApache-2.0
Termux Safeferrumclaudepilgrim/claude-code-android268—~935Automated safety check: PassMIT
Crash Instrumentationnexus-labs-automation/mobile-observability116—~744Automated safety check: PassMIT
Network Tracingnexus-labs-automation/mobile-observability116—~672Automated safety check: PassMIT

Similar skills

  • Gradle Build Performance

    Moustachauve/WLED-Android

    Debug and optimize Android/Gradle build performance. An agent skill from Moustachauve/WLED-Android.

    169 GitHub starsUsed in 3 repos~2k tokens
    DevOps & CloudAuto-check passed
  • GitHub Workflows

    amirisback/automated-build-android-app-with-github-action

    Manage and automate Android CI/CD workflows using GitHub Actions in this repository.

    346 GitHub stars~550 tokensUpdated 26 days ago
    DevOps & CloudAuto-check passed
  • Termux Safe

    ferrumclaudepilgrim/claude-code-android

    Android/Termux constraints reference. An agent skill from ferrumclaudepilgrim/claude-code-android.

    268 GitHub stars~935 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Crash Instrumentation

    nexus-labs-automation/mobile-observability

    Set up crash instrumentation with actionable context. An agent skill from nexus-labs-automation/mobile-observability.

    116 GitHub stars~744 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Network Tracing

    nexus-labs-automation/mobile-observability

    Instrument API requests with spans and distributed tracing. An agent skill from nexus-labs-automation/mobile-observability.

    116 GitHub stars~672 tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Cleanup

    cua-lite/cua-lite

    Direct-mode cleanup of local docker containers, training processes, and GPU memory.

    108 GitHub stars~1.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from hanamizuki/solopreneur

All 31 skills in this repo
  • Preview

    hanamizuki/solopreneur

    Create an interactive HTML preview of any proposal, plan, idea, doc, brief, or spec and land it in the browsable local Preview Library by default (opens under file:// with a catalog sidebar and…

    152 GitHub stars~5.2k tokensUpdated 14 days ago
    Auto-check passed
  • iOS Patterns

    hanamizuki/solopreneur

    A skill your agent uses when building iOS/macOS apps with SwiftUI — covers localization (String Catalogs), date/time formatting, JSON date decoding, Previews, state management, sheet/navigation…

    152 GitHub stars~2.3k tokensUpdated 14 days ago
    Auto-check: notes
  • Linkedin Growth

    hanamizuki/solopreneur

    LinkedIn organic growth consultant — diagnoses profiles, discusses goals, and co-creates a personalized 90-day growth plan.

    152 GitHub stars~3.7k tokensUpdated 14 days ago
    Auto-check passed
  • Perspective

    hanamizuki/solopreneur

    Switch perspectives to think through problems using the mental models of ten iconic thinkers: Elon Musk, Richard Feynman, Charlie Munger, Naval Ravikant, Steve Jobs, Nassim Taleb, Ilya Sutskever…

    152 GitHub stars~971 tokensUpdated 14 days ago
    Auto-check passed
  • Slide Design

    hanamizuki/solopreneur

    Create brand-aware presentations using frontend-slides or reveal.js.

    152 GitHub stars~3.9k tokensUpdated 14 days ago
    Auto-check passed
  • X Growth

    hanamizuki/solopreneur

    X/Twitter growth consultant — diagnoses profiles, discusses goals, and co-creates a personalized growth plan.

    152 GitHub stars~3.8k tokensUpdated 14 days ago
    Auto-check passed

Works with

Categories

Questions about Gplay Rollout Management

What does Gplay Rollout Management do?

Staged rollout orchestration and monitoring for Google Play releases. Gplay Rollout Management is an agent skill from hanamizuki/solopreneur. Staged rollout orchestration and monitoring for Google Play releases.

When should I use Gplay Rollout Management?

Gplay Rollout Management fits situations like: implementing gradual release strategies.

How do I install Gplay Rollout Management in Claude Code?

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

How do I install Gplay Rollout Management in Codex?

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

Can I use Gplay Rollout Management 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-rollout-management -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-rollout-management, .gemini/skills/gplay-rollout-management, .github/skills/gplay-rollout-management and .opencode/skills/gplay-rollout-management in your project.

What does Gplay Rollout Management need to run?

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

Does Gplay Rollout Management 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 Rollout Management 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 Rollout Management use?

Gplay Rollout Management 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 Rollout Management use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 Rollout Management?

Skills that share tags, products or a category with Gplay Rollout Management: Gradle Build Performance (Moustachauve/WLED-Android, 169 stars), GitHub Workflows (amirisback/automated-build-android-app-with-github-action, 346 stars), Termux Safe (ferrumclaudepilgrim/claude-code-android, 268 stars) and Crash Instrumentation (nexus-labs-automation/mobile-observability, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gplay Rollout Management?

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.