skills.rest
JCETools-Petra
JCETools-PetraCOMMUNITY
Explore all skills by this author →
GitHub

android-release

Build and verify Android APK/AAB release builds with signing and R8/ProGuard.

16|Updated Apr 30, 2026
Search Tags:#versioning#android#signing#play console#release build#r8 proguard
One-click install
npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill android-release-jcetools-petra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-release
Source: https://github.com/JCETools-Petra/JCE-Opencode-Tools/tree/main/config/skills/android-release
Command: npx skills add https://github.com/JCETools-Petra/JCE-Opencode-Tools --skill android-release-jcetools-petra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents release breakages by guiding you through Android APK/AAB packaging, signing, and release-only verification so your Play-ready artifacts are consistent with your source and build configuration.

Core Features & Use Cases

  • Release build correctness: Builds the right artifact types (APK/AAB) and validates release pipelines rather than relying on debug results.
  • Signing and ProGuard/R8 readiness: Checks signingConfig/keystore correctness and ensures R8/ProGuard behavior with mapping.txt awareness.
  • Versioning and Play Console readiness: Guards against versionCode/versionName drift and release-only gaps that appear only in release tasks.
  • Use Case: Before publishing to the Play Console, ensure your bundleRelease output is correctly signed, properly minified, and consistent with expected versioning across a production rollout.

Quick Start

Ask the AI to prepare and verify a production release by running bundleRelease and lintVitalRelease, then reporting any signing, minification, versioning, or release-only gaps it finds.

Frequently Asked Questions about android-release

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

FAQPage Schema
How do I prepare a signed Android AAB release build for the Play Console?▼

To prepare a signed Android AAB, configure your signingConfig with a valid keystore and run the bundleRelease gradle task to generate a Play Console ready artifact.

Why does my Android release build fail with R8 ProGuard missing classes?▼

Android release builds fail with R8 ProGuard missing classes when minification strips required code. You must explicitly add keep rules and verify the mapping.txt file to resolve release-only failures.

How do I check versionCode and versionName drift before an Android release rollout?▼

Check versionCode and versionName drift by running release readiness verifications like lintVitalRelease to ensure your build outputs are consistent with expected versioning across a production rollout.

What is the difference between assembleRelease and bundleRelease for Android packaging?▼

The difference between assembleRelease and bundleRelease is the artifact type: assembleRelease packages an APK, while bundleRelease generates an AAB optimized for Play Console distribution.

When do I need to run lintVitalRelease checks for an Android production rollout?▼

You need to run lintVitalRelease checks before an Android production rollout to explicitly detect release-only gaps, signing mismatches, and minification issues that do not appear in debug builds.

Related Skills

Explore More Software Engineering Skills→
JCE-Joshhh77JCE-Joshhh77
16

android-release

Coordinate Android release packaging and signing workflows for APKs and AABs.

Community
Advanced
cslsoftwarescslsoftwares

developer-delphi-android-publishing

Automate keystore management, signing, and Play Console publishing for Delphi FMX Android apps.

Community
Advanced
uyelikaniluyelikanil

r8-analyzer

Analyze Android R8 keep rules and Gradle settings for optimization opportunities.

Community
Advanced
hanamizukihanamizuki
127

gplay-gradle-build

Build, sign, and package Android apps with Gradle for Google Play.

Community
Intermediate