What problem does it solve?
Setting up an Android release pipeline to Google Play involves many error-prone manual steps: keystore generation, signing configuration, GitHub Secrets management, versionCode bumping, and multi-track publishing. This Skill automates the entire setup so pushes to main and version tags trigger the correct Google Play track releases.
Core Features & Use Cases
- Interactive Setup Wizard: Run npx android-cicd to auto-detect your framework (TWA, React Native, Flutter, or native Android), generate an upload keystore, configure GitHub Secrets via the gh CLI, and scaffold the GitHub Actions workflow.
- Multi-Stage Publishing: Pushes to main publish to the internal track, while tags like v1.2-alpha, v1.2-beta, and v1.2.0 publish to alpha, beta, and production tracks respectively.
- Automatic versionCode Bumping: On every push to main, CI increments the versionCode in the framework-appropriate file (build.gradle or pubspec.yaml) and commits it with [skip ci].
- Use Case: A developer with a Flutter app tracked on GitHub runs the wizard, completes the one-time Google Play service account setup, and from then on ships production releases simply by pushing a version tag.
Quick Start
Ask the assistant to set up an Android CI/CD pipeline for your project by running npx android-cicd from the project root and following the interactive wizard.