Skip to content
cccskills
FreePublished on GitHub

android-play-release

Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Android Play Release

Get an Android build onto Google Play without the classic policy/upload blockers, and release it with a safety lever. Belongs to the play-store-release-specialist discipline. Run it before every Play upload; the checks are cheap and the failures are expensive (rejection or a bad rollout).

Arguments

  • path-to-android-project — the project directory to check (defaults to the current directory).

Steps

1. Run the pre-flight checks

python -m android_preflight.cli <project-dir> [--play-min-target N]

Resolve every ERROR before uploading, and run ./gradlew lint (the checker doesn't reimplement Android Lint). The checker flags:

  • Sensitive permissions — background location is an ERROR (needs a Play declaration with one core feature + demo video); other restricted permissions are warnings.
  • Exported components with no permission/intent-filter (any app can invoke them).
  • targetSdk below the Play minimum (blocks new apps/updates; hidden on new devices — version-sensitive).
  • Release config — no R8 (minifyEnabled), debug signing config, or committed secrets.
  • debuggable/usesCleartextTraffic in the manifest.

2. Clear the Play policy/console gates

  • Data Safety form completed and matching app + third-party-SDK behaviour (mismatch = rejection).
  • Account deletion (in-app + web URL) if the app has accounts; privacy policy URL live; content rating (IARC); ads/target-audience declarations.
  • Sensitive-permission declarations with justification + demo video where required.

3. Build a signed app bundle

  • versionCode unique & monotonic — stamp from git rev-list --count HEAD (or CI build number).
  • ./gradlew bundleRelease → a signed .aab (Play requires the bundle format). Verify locally with bundletool (build-apks / install-apks) — the exact split APKs Play will serve.

4. Upload to a track and roll out deliberately

  • Upload to internal testing first (available in minutes, no review) to smoke-test; then closed/ open (external needs the metadata above); then production.
  • On production, use a staged (percentage) rollout starting small (e.g. 5–10%), and watch Android vitals (user-perceived crash ≥1.09% overall / ≥8% per-device, ANR ≥0.47% / ≥8% gate discoverability).
  • Automate via the Play Developer API (edits flow: insert → bundles.upload → tracks.update → commit), Gradle Play Publisher (com.github.triplet.play), or fastlane supply — all with service-account JSON auth.

5. Halt / roll forward on regression (the Play advantage)

  • If vitals regress mid-rollout, Halt rollout (the kill switch iOS lacks). Recover by rolling forward: publish a higher-versionCode fixed release to the same track (there is no literal byte revert — versionCode is monotonic). Consider an immediate in-app update for critical fixes.

6. Report

Summarise: pre-flight result (errors fixed), the versionCode and the commit it maps to, the track it went to, the rollout percentage, and the policy gates cleared. State anything outstanding (e.g. Data Safety not yet complete) rather than implying the release is ready.

Notes

  • Play policy dates/API levels/vitals thresholds are version-sensitive — re-verify against the live Google docs.
  • Always ship production behind a staged rollout so you retain the halt lever.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

Generate boilerplate `# implements:` annotation for a function based on the artefact ID, inserting it as the first line of the function body.

The English summary is being prepared. Showing the original description.

SteveGJones/ai-first-sdlc-practices41Updated Oct 5, 2026

See all skills by SteveGJones

Report a problem with this skill