android-playstore-publishing_skill

This skill automates end-to-end Android Play Store publishing by generating internal, beta, and production workflows with validation.
  • Shell

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill hitoshura25/claude-devtools --skill android-playstore-publishing

  • SKILL.md5.1 KB

Overview

This skill orchestrates end-to-end GitHub Actions workflow generation for Play Store deployments, creating internal, beta, and production pipelines. It runs three atomic generators in sequence and verifies workflows, secrets, and environment configuration to ensure a safe staged release process.

How this skill works

The skill generates three workflows: deploy-internal.yml (automatic on push), deploy-beta.yml (manual trigger for alpha/beta with configurable rollout), and deploy-production.yml plus manage-rollout.yml (manual approval and staged rollout control). After generation it runs YAML validation and checks package names and secret references. Final verification steps confirm files exist, are valid, and reference the required secrets and environment.

When to use it

  • Setting up CI/CD for Android apps targeting Google Play with internal, beta, and production tracks
  • Automating safe staged rollouts that require approvals and rollout percentage control
  • Standardizing workflow generation across multiple repositories
  • Onboarding new apps where Play Console and signing are already configured
  • When you need reproducible, linted GitHub Actions for Play Store publishing

Best practices

  • Run android-playstore-setup first to provision service account and API access
  • Store SERVICE_ACCOUNT_JSON_PLAINTEXT and signing values as GitHub Secrets before running
  • Create a 'production' GitHub environment and configure required reviewers in advance
  • Validate generated YAML with yamllint and verify packageName and secrets references
  • Start production rollouts at 5% and monitor crash-free rate before increasing

Example use cases

  • Automatically deploy developer builds to the internal track on push to main or develop
  • Manually promote releases to alpha or beta with configurable rollout percentages
  • Gate production releases with environment approval and perform staged rollouts
  • Standardize publishing across a mono-repo with multiple Android modules
  • Recover from a failed sub-skill: fix the specific workflow and re-run verification

FAQ

You must add SERVICE_ACCOUNT_JSON_PLAINTEXT and signing secrets: SIGNING_KEY_STORE_BASE64, SIGNING_KEY_ALIAS, SIGNING_STORE_PASSWORD, SIGNING_KEY_PASSWORD.

Do I need a GitHub environment?

Yes. Create a 'production' environment and configure required reviewers before running production deployments.

How do I verify the generated workflows?

Check files exist under .github/workflows, run yamllint on each workflow, grep for packageName and secrets to ensure correctness, and ensure environment usage is set for production.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational