android-release-notes-structure

Create locale-aware Android release notes directories with fastlane metadata templates.

3|1|Updated Dec 4, 2025

Search Tags:#documentation #metadata #android #fastlane #release-notes #multi-locale

Ready to run

npx skills add https://github.com/hitoshura25/claude-devtools --skill android-release-notes-structure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-release-notes-structure
Source: https://github.com/hitoshura25/claude-devtools/tree/main/skills/android-release-notes-structure
Command: npx skills add https://github.com/hitoshura25/claude-devtools --skill android-release-notes-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of a locale-aware Android release notes directory structure for Play Store metadata, saving time and ensuring consistency across locales.

Core Features & Use Cases

Create the fastlane/metadata/android directory scaffold with per-locale changelogs directories.
Generate default.txt templates for each locale and a centralized README and tracks documentation.
Ideal for release engineers and developers who publish Android apps and need standardized release notes across locales.

Quick Start

Define locales to support (default: en-US). Run the skill to generate the directory structure and templates under fastlane/metadata/android. Verify the setup with the provided checks: ensure fastlane/metadata/android/en-US/changelogs exists and that a default.txt file has been created for each locale.

Frequently Asked Questions about android-release-notes-structure

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

FAQPage Schema

How do I create multi-locale Android release notes for the Play Store?▼

To create multi-locale Android release notes, you need a structured directory scaffold under fastlane/metadata/android with per-locale changelogs and default.txt templates. This ensures standardized Play Store metadata across different languages during deployment.

What is the fastlane metadata directory structure for Android release notes?▼

The fastlane metadata directory structure for Android release notes organizes files into fastlane/metadata/android/${locale}/changelogs directories. Each locale folder contains a default.txt template for standardized changelog entries.

How do I set up fastlane metadata for multiple Android locales?▼

Setting up fastlane metadata for multiple Android locales involves defining your target locales and generating a directory scaffold with per-locale changelogs, default.txt templates, and centralized documentation like a README and tracks reference.

Does fastlane require a specific directory structure for Play Store release notes?▼

Fastlane requires a specific locale-aware directory structure under fastlane/metadata/android to publish Play Store release notes correctly. This includes per-locale changelogs directories and default.txt files to ensure automated deployment processes can locate the metadata.

What's the best way to manage Play Store release notes across different locales?▼

The best way to manage Play Store release notes across locales is to use an automated directory scaffold with per-locale default.txt templates and a centralized README. This approach ensures consistency and saves time during multi-locale app publishing.

Can I verify my fastlane Android metadata setup before deployment?▼

You can verify your fastlane Android metadata setup by running a simple verification step to confirm the directory structure exists. This check ensures fastlane/metadata/android/en-US/changelogs is present and a default.txt file has been created for each locale.