android-keystore-generation

Generate Android signing keystores for production and local development.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of Android signing keystores for both production releases (CI/CD) and local development, eliminating manual, error-prone steps and ensuring consistent signing configurations.

Core Features & Use Cases

  • Dual keystore generation: Produces production-release.jks for CI/CD and local-dev-release.jks for local testing.
  • Credential documentation: Generates KEYSTORE_INFO.txt with all necessary credentials and GitHub secret instructions.
  • Environment hygiene: Updates .gitignore to ignore keystore files to protect sensitive data.
  • Use Case: Integrate into a feature branch workflow to sign builds automatically with production and local keys.

Quick Start

Use this skill in your Android project root to generate and document signing keys. The workflow will prompt for organization name, password handling, and then create the keystores and the credentials file.

Frequently Asked Questions about android-keystore-generation

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

FAQPage Schema
How do I generate an Android signing keystore for CI/CD and local development?

Android keystore generation automates creating production-release.jks for CI/CD and local-dev-release.jks for local testing. It applies proper Distinguished Name details, manages passwords, and updates .gitignore to protect sensitive keystore files.

What credentials do I need to configure GitHub Secrets for Android signing?

Android signing credentials require keystore passwords, key aliases, and key passwords. This Skill generates a KEYSTORE_INFO.txt file documenting all necessary credentials alongside specific instructions for configuring them as GitHub Secrets.

How do I securely manage Android keystore files in a Gradle project?

Secure Android keystore management involves adding keystore files to .gitignore to prevent committing sensitive data. This Skill automatically updates .gitignore while generating separate production and local keystores for your Gradle project.

Can I automate keystore creation for an Android release workflow without manual keytool commands?

Automating Android keystore creation eliminates manual keytool and OpenSSL steps. This Skill prompts for organization name and password handling, then automatically generates both production and local keystores with proper configuration.

Do I need separate keystores for local testing and production Android releases?

Yes, separating Android keystores for production and local development ensures CI/CD security and local testing flexibility. This Skill generates distinct production-release.jks and local-dev-release.jks files to isolate signing environments.

Why does my Android keystore generation require Distinguished Name details?

Android keystore generation requires Distinguished Name details to identify the certificate owner for release signing. This Skill ensures proper DN details are applied during creation, producing valid keystores for both production and local environments.