android-release-validation

Validate Android release builds for signing, obfuscation, and packaging.

3|1|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/hitoshura25/claude-devtools --skill android-release-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-release-validation
Source: https://github.com/hitoshura25/claude-devtools/tree/main/skills/android-release-validation
Command: npx skills add https://github.com/hitoshura25/claude-devtools --skill android-release-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Android release validation ensures that production builds are signed correctly, obfuscated safely, and packaged without issues before publishing, preventing crashes and policy rejections.

Core Features & Use Cases

  • Sign and verify APK/AAB during release
  • Validate ProGuard/R8 mapping presence and accuracy
  • Run smoke E2E tests on release builds to catch breakages

Quick Start

Use the android-release-validation skill to validate your current Android release build artifacts.

Frequently Asked Questions about android-release-validation

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

FAQPage Schema
How do I validate an Android release build before publishing?

To validate an Android release build, you must verify APK and AAB generation, check signing validity, confirm ProGuard or R8 mapping file existence, and run smoke E2E device tests to ensure production readiness.

What does ProGuard mapping file validation check for in Android release builds?

ProGuard mapping file validation checks for the existence and accuracy of obfuscation mappings generated by R8 or ProGuard, ensuring that obfuscated release builds can be deobfuscated and traced correctly during crashes.

Can I use this validation process with my existing Gradle Android project?

Yes, this validation process applies directly to Android projects using Gradle, integrating with your existing release testing workflows to verify APK and AAB artifacts and enforce signing and compatibility metadata checks.

Why do I need to verify APK and AAB signing for production release?

Verifying APK and AAB signing prevents production crashes and app store policy rejections by ensuring that release builds are signed correctly, obfuscated safely, and packaged without issues before publishing to users.

How do smoke E2E tests catch breakages in Android release builds?

Smoke E2E tests run directly on release builds to catch obfuscation-induced breakages and packaging issues, verifying device compatibility and application behavior before the final production deployment.