android-playstore-pipeline_skill

Overview

This skill automates a complete end-to-end Android Play Store deployment pipeline in one command. It runs five prerequisite setup steps—release build, E2E testing, release validation, Play Console integration, and CI/CD publishing—so you get a production-ready pipeline from scratch. The tool is interactive and validates every component before finishing. It saves time and enforces safety checks for keystores, tests, and workflows.

How this skill works

You answer a short interactive questionnaire once; the skill then executes all five setup tasks in the correct order. It generates keystores, configures signing and ProGuard/R8, creates Espresso tests and CI test workflows, builds release validation scripts, scaffolds Play Console integration docs, and emits GitHub Actions deployment workflows. A mandatory end-to-end validation step runs build, test, Play Console checks, and workflow linting; the pipeline completes only if every check passes.

When to use it

• You have an Android Gradle project and want a turnkey Play Store pipeline.
• You need to add signing, E2E tests, and CI/CD workflows quickly.
• You’re preparing to publish to Google Play and need Play Console integration.
• You want staged rollouts, multi-track deployment, and approval gates.
• You prefer a single command orchestration that validates all prerequisites.

Best practices

• Run the interactive questionnaire from your project root to avoid path errors.
• Store generated keystore passwords in a secure password manager and never commit keystores.
• Add required GitHub Secrets and create a protected production environment before enabling production workflows.
• Run the mandatory validation step and fix any failing skill before marking the pipeline complete.
• Test the pipeline by deploying to the internal track before promoting to beta or production.

Example use cases

• Set up a new Android app’s CI/CD so QA can access builds via Play internal testing within minutes.
• Add signing and ProGuard configuration to an existing app without manual gradle edits.
• Create sample Espresso tests and CI test workflows for teams new to instrumented testing.
• Automate staged production rollouts with manual approval gates for regulated releases.
• Prepare release notes and GitHub Secrets documentation for handoff to release engineers.