
Gplay Gradle Build
This handles the Gradle build pipeline for Android apps heading to Google Play, covering both AAB and APK builds with proper signing configuration. You'll use it when you need to set up release builds, configure ProGuard/R8 minification, or automate version bumping before uploads. The signing setup uses environment variables instead of hardcoded credentials, which is the right call. It includes CI/CD examples for GitHub Actions and shows how to generate and upload ProGuard mapping files for crash symbolication. The troubleshooting section covers keystore verification and bundletool commands for inspecting AAB contents. Solid reference if you're wiring up Android release automation and don't want to dig through Gradle docs.
- skills.sh installs
- 420
- GitHub stars
- 52
- last updated
- Aug 21, 2026
Install
$ npx -y skills add tamtom/gplay-cli-skills --skill gplay-gradle-build --agent claude-codeInstalls into .claude/skills of the current project.
Files
Gradle Build for Google Play
Use this skill when you need to build an Android app before uploading to Play Store.
Build Types
App Bundle (AAB) - Recommended
App Bundles are required for new apps on Google Play:
./gradlew bundleRelease
Output: app/build/outputs/bundle/release/app-release.aab
APK - Legacy
For apps not using bundles:
./gradlew assembleRelease
Output: app/build/outputs/apk/release/app-release.apk
Signing Configuration
build.gradle (app level)
android {
signingConfigs {
release {
storeFile file(System.getenv("KEYSTORE_FILE") ?: "release.keystore")
storePassword System.getenv("KEYSTORE_PASSWORD")
keyAlias System.getenv("KEY_ALIAS")
keyPassword System.getenv("KEY_PASSWORD")
}
}
buildTypes {
release {
signingConfig signingConfigs.release
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
}
}
}
Sponsors
Details
- Repository
- github.com/tamtom/gplay-cli-skills
- Categories
- DevOps & CI/CD, Mobile Development, Java & JVM, CLI & Terminal
- First seen
- Jun 3, 2026