What problem does it solve? Preparing an Android app for Google Play requires correctly configuring Gradle builds, signing credentials, version codes, and ProGuard mapping files, and mistakes in any of these steps cause failed uploads or broken releases. ## Core Features & Use Cases - Release Builds: Generate signed AAB (recommended) or APK artifacts with ./gradlew bundleRelease or assembleRelease. - Signing & Versioning: Configure keystore credentials via environment variables and manage versionCode/versionName through gradle.properties. - CI/CD Integration: Build and upload releases in GitHub Actions, including ProGuard mapping file upload for crash symbolication. - Use Case: You need to ship a new release to the Play internal track. Use this Skill to increment the version code, build a signed AAB, and upload it with the gplay CLI in one workflow. ## Quick Start Build a signed release App Bundle for my Android project and increment the version code before uploading it to Google Play.