skills.rest
JCE-Joshhh77
JCE-Joshhh77COMMUNITY
Explore all skills by this author →
WebsiteGitHub

android-release

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

16|Updated Apr 30, 2026
Search Tags:#versioning#build#release#android#gradle#signing#keystore
One-click install
npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill android-release-jce-joshhh77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-release
Source: https://github.com/JCE-Joshhh77/JCE-Opencode-Tools/tree/main/config/skills/android-release
Command: npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill android-release-jce-joshhh77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines Android release management by automating packaging, signing, and readiness checks for APKs and AABs, reducing manual errors in versioning and deployment.

Core Features & Use Cases

  • Automated release packaging: bundleRelease/assembleRelease for APKs and AABs.
  • Signing and keystore management: ensures correct signing configs and keystore usage.
  • Versioning guardrails: enforces versionCode and versionName consistency across builds.
  • Play Console readiness: validates mapping.txt, ProGuard/R8 configuration, and signing alignment.

Quick Start

Prepare an end-to-end Android release plan including signing, versioning, and Play Console readiness for a new app module.

Frequently Asked Questions about android-release

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

FAQPage Schema
How do I automate Android release builds and signing for APKs and AABs?▼

Automate Android release builds by coordinating assembleRelease and bundleRelease workflows, applying correct signing configurations and keystore management to generate signed APKs and AABs.

How does ProGuard and R8 optimization affect Play Console readiness?▼

ProGuard and R8 optimization affects Play Console readiness by obfuscating code, requiring validation of mapping.txt to ensure crash deobfuscation and correct release alignment.

What's the best way to manage versionCode and versionName consistency across build variants?▼

Manage versionCode and versionName consistency by applying versioning guardrails that enforce deterministic values across all build variants during the release packaging process.

Why does my Android release build fail keystore validation in CI/CD pipelines?▼

Android release build keystore validation fails when signing configurations are incorrect or non-deterministic, requiring strict enforcement of keystore usage and release-specific constraints across CI/CD pipelines.

Do I need a valid mapping.txt file to publish an Android AAB to the Play Console?▼

Yes, you need a valid mapping.txt file to publish an Android AAB to the Play Console, as it validates ProGuard/R8 configuration and ensures proper crash report deobfuscation.

Can I use Gradle to enforce deterministic builds for Android release variants?▼

Yes, you can use Gradle to enforce deterministic builds for Android release variants by verifying release-specific constraints, applying correct signing configs, and validating versionCode consistency.

Related Skills

Explore More Software Engineering Skills→
JCETools-PetraJCETools-Petra
16

android-release

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

Community
Intermediate
decentpastedecentpaste
232

android-release

Build, sign, and align Android APKs and AABs for GitHub and Play Console releases.

Official
Intermediate
fornewidfornewid
5

https://developer.android.com/agents/skills/performance/r8-analyzer/skill

Audit ProGuard/R8 keep-rule impact on Android shrinking and obfuscation.

Community
Intermediate
po4ykapo4yka
58

release-signing

Automate APK/AAB signing and release preparation for Android CI/CD workflows.

Community
Advanced