android-release-build-setup
Complete Android release build configuration - orchestrates keystore, ProGuard, and signing setup
Best use case
android-release-build-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Complete Android release build configuration - orchestrates keystore, ProGuard, and signing setup
Teams using android-release-build-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/android-release-build-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How android-release-build-setup Compares
| Feature / Agent | android-release-build-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Complete Android release build configuration - orchestrates keystore, ProGuard, and signing setup
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Android Release Build Setup
This skill orchestrates complete Android release build configuration by running three atomic skills in sequence.
## What This Does
Sets up everything needed for Android release builds:
1. **Keystore Generation** - Production and local dev keystores
2. **ProGuard/R8 Configuration** - Code minification and optimization
3. **Signing Configuration** - Dual-source signing (CI/CD + local dev)
## Prerequisites
- Android project with Gradle
- JDK installed (for keytool command)
- Project uses Kotlin DSL (build.gradle.kts)
## Process
This skill runs three sub-skills in order:
### Step 1: Generate Keystores
Follow the skill at: `~/claude-devtools/skills/android-keystore-generation/SKILL.md`
**What it does:**
- Creates production keystore (for CI/CD only)
- Creates local development keystore
- Generates KEYSTORE_INFO.txt with credentials
- Updates .gitignore
**Verify before continuing:**
```bash
ls keystores/*.jks
cat keystores/KEYSTORE_INFO.txt
```
---
### Step 2: Configure ProGuard/R8
Follow the skill at: `~/claude-devtools/skills/android-proguard-setup/SKILL.md`
**What it does:**
- Creates proguard-rules.pro with safe defaults
- Enables minification in build.gradle.kts
- Enables resource shrinking
**Verify before continuing:**
```bash
test -f app/proguard-rules.pro
grep "isMinifyEnabled = true" app/build.gradle.kts
```
---
### Step 3: Configure Signing
Follow the skill at: `~/claude-devtools/skills/android-signing-config/SKILL.md`
**What it does:**
- Adds signingConfigs to build.gradle.kts
- Creates gradle.properties.template
- Configures ~/.gradle/gradle.properties (with permission)
- Adds validation for missing signing config
**Verify before continuing:**
```bash
./gradlew assembleRelease
jarsigner -verify app/build/outputs/apk/release/app-release.apk
```
---
## Final Verification (MANDATORY)
After all three skills complete, verify the complete setup:
```bash
# 1. Clean build
./gradlew clean
# 2. Build release APK
./gradlew assembleRelease
# 3. Verify APK exists
ls -lh app/build/outputs/apk/release/app-release.apk
# 4. Verify ProGuard mapping generated
ls -lh app/build/outputs/mapping/release/mapping.txt
# 5. Verify signing
jarsigner -verify -verbose -certs app/build/outputs/apk/release/app-release.apk
```
**All checks must pass** before marking this skill as complete.
## Completion Criteria
Do NOT mark complete unless ALL are verified:
✅ **Keystores generated and secured**
- [ ] production-release.jks exists in keystores/
- [ ] local-dev-release.jks exists in keystores/
- [ ] KEYSTORE_INFO.txt created with passwords
- [ ] keystores/ added to .gitignore
✅ **ProGuard configured**
- [ ] proguard-rules.pro exists with safe defaults
- [ ] isMinifyEnabled = true in build.gradle.kts
- [ ] isShrinkResources = true in build.gradle.kts
✅ **Signing configured**
- [ ] signingConfigs.release exists in build.gradle.kts
- [ ] Release buildType uses signingConfig
- [ ] gradle.properties configured (local) OR environment variables set (CI)
✅ **MANDATORY: Build verification**
- [ ] `./gradlew assembleDebug` succeeds
- [ ] `./gradlew assembleRelease` succeeds
- [ ] app/build/outputs/apk/release/app-release.apk exists
- [ ] app/build/outputs/mapping/release/mapping.txt exists
- [ ] `jarsigner -verify` confirms APK is signed correctly
## Summary Report
After completion, provide this summary:
```
✅ Android Release Build Setup Complete!
📦 Keystores Generated:
Production: keystores/production-release.jks (CI/CD only)
Local Dev: keystores/local-dev-release.jks (local testing)
Credentials: keystores/KEYSTORE_INFO.txt
🔒 ProGuard/R8 Configuration:
✓ Minification enabled
✓ Resource shrinking enabled
✓ Safe default rules: app/proguard-rules.pro
⚙️ Build Configuration:
✓ Signing config added to app/build.gradle.kts
✓ Dual-source strategy (env vars + gradle.properties)
✓ Validation on release builds
📋 Next Steps:
For Local Development:
./gradlew assembleRelease
./gradlew installRelease
For CI/CD (GitHub Actions):
Add GitHub Secrets (see KEYSTORE_INFO.txt):
- SIGNING_KEY_STORE_BASE64
- SIGNING_KEY_ALIAS
- SIGNING_STORE_PASSWORD
- SIGNING_KEY_PASSWORD
⚠️ CRITICAL REMINDERS:
- NEVER commit keystores to git
- NEVER use production keystore locally
- ALWAYS back up production keystore securely
- Loss of production keystore = cannot update app!
```
## Integration with Other Skills
This skill is prerequisite for:
- `android-e2e-testing-setup` - Tests release builds
- `android-release-validation` - Validates signed APK/AAB
- `android-playstore-publishing` - Uses keystore for CI/CD workflow
- `android-playstore-pipeline` - Orchestrates full setup
## Troubleshooting
If any skill fails:
1. Fix the specific issue in that skill
2. Re-run that skill until it completes
3. Continue with remaining skills
4. Run final verification
Common issues:
- **Keystore generation fails** → Install JDK
- **ProGuard breaks build** → Add keep rules
- **Signing fails** → Check gradle.properties pathsRelated Skills
conductor-setup
Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)
cc-soul-setup
Build cc-soul from source (requires cmake, make, C++ compiler)
buildlog
Record, export, and share your AI coding sessions as replayable buildlogs
buildkite-automation
Automate Buildkite tasks via Rube MCP (Composio). Always search tools first for current schemas.
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
building-mechanics
Three.js 3D building system with spatial indexing, structural physics, and multiplayer networking. Use when creating survival games, sandbox builders, or any game with player-constructed structures. Covers performance optimization (spatial hash grids, octrees, chunk loading), structural validation (arcade/heuristic/realistic physics modes), and multiplayer sync (delta compression, client prediction, conflict resolution).
building-github-index
Generate progressive disclosure indexes for GitHub repositories to use as Claude project knowledge. Use when setting up projects referencing external documentation, creating searchable indexes of technical blogs or knowledge bases, combining multiple repos into one index, or when user mentions "index", "github repo", "project knowledge", or "documentation reference".
building-ai-chat
Builds AI chat interfaces and conversational UI with streaming responses, context management, and multi-modal support. Use when creating ChatGPT-style interfaces, AI assistants, code copilots, or conversational agents. Handles streaming text, token limits, regeneration, feedback loops, tool usage visualization, and AI-specific error patterns. Provides battle-tested components from leading AI products with accessibility and performance built in.
builder-workflow
Phase-level implementation workflow for builder agents. Handles loading project rules, reading phase files, finding references, invoking domain skills, implementing all steps, and running verification (tests + typecheck). Invoke this skill as your first action — not user-invocable.
BuildAgent
Create, validate, or audit agent definitions. USE WHEN create agent, new agent, build agent, scaffold agent, validate agent, audit agents, agent conventions, agent frontmatter.
build
Build features with AI coding tools (Claude Code, Lovable, Replit, Cursor). Use when implementing specs, iterating on AI code, or choosing tools. Focuses on tool selection, effective prompting, and iteration workflows for non-technical founders.
Build Your Pipecat Skill
Create your Pipecat skill from official documentation, then learn to improve it throughout the chapter