android-cicd

Automates Android CI/CD pipeline setup for publishing builds to Google Play via GitHub Actions.

30.5k|3.5k|Updated Jul 4, 2025
One-click install
npx skills add https://github.com/davila7/claude-code-templates --skill android-cicd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-cicd
Source: https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/development/android-cicd
Command: npx skills add https://github.com/davila7/claude-code-templates --skill android-cicd

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about android-cicd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an Android CI/CD pipeline to Google Play with GitHub Actions?

Run npx android-cicd from your project root. The interactive wizard detects your framework, generates an upload keystore, sets the required GitHub Secrets via the gh CLI, and scaffolds a multi-stage workflow that publishes to Google Play tracks.

How do I release an Android app to production on Google Play using git tags?

Increment the versionCode manually, commit, then create and push a tag like v1.2.0. The workflow maps tag patterns to tracks: v*-alpha to alpha, v*-beta to beta, and plain v* tags to production.

Does android-cicd support Flutter and React Native projects?

Yes, the wizard auto-detects Flutter via pubspec.yaml, React Native via android/app/build.gradle plus a react-native dependency, TWA via Bubblewrap files, and native Android via build.gradle. You can override the detected framework during setup.

Why does my Google Play upload fail with a wrong versionCode error?

Tag-based builds for alpha, beta, and production do not auto-increment the versionCode, since tags represent pinned commits. Increment versionCode manually in build.gradle or pubspec.yaml before creating and pushing the release tag.

What manual steps are required before the Google Play API can publish builds?

You must create a Google Cloud service account with a JSON key, enable the Google Play Android Developer API, invite the service account in Play Console with release permissions, and upload at least one AAB manually before API publishing works.

How do I recover a lost Android upload keystore?

If the app uses Play App Signing, generate a new keystore with npx android-cicd, export its PEM certificate with keytool, then request an upload key reset in Play Console under App integrity. Update the KEYSTORE_FILE secret after Google approves.