gplay-migrate-fastlane

Convert Fastlane Android metadata directories into gplay CLI listing.json format.

43|6|Updated Feb 5, 2026

Search Tags:#release management #migration #metadata #android #fastlane #gplay

Ready to run

npx skills add https://github.com/tamtom/gplay-cli-skills --skill gplay-migrate-fastlane

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gplay-migrate-fastlane
Source: https://github.com/tamtom/gplay-cli-skills/tree/main/skills/gplay-migrate-fastlane
Command: npx skills add https://github.com/tamtom/gplay-cli-skills --skill gplay-migrate-fastlane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the conversion of existing Fastlane metadata directories into the format required by the gplay CLI, streamlining the transition for Android app release management.

Core Features & Use Cases

Fastlane to gplay Migration: Converts Fastlane's directory structure and files (like title.txt, short_description.txt) into gplay's listing.json and maintains image and changelog structures.
Selective Locale Migration: Allows migrating specific locales or performing a dry run to preview changes before committing.
Use Case: You have a mature Android app managed with Fastlane for Play Store deployments. To leverage the gplay CLI's features, you use this skill to migrate your existing metadata (descriptions, screenshots, etc.) with minimal manual effort.

Quick Start

Use the gplay-migrate-fastlane skill to migrate your Fastlane metadata located at './fastlane/metadata/android' to './metadata' and preview the changes without writing files.

Frequently Asked Questions about gplay-migrate-fastlane

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

FAQPage Schema

How do I migrate Android app metadata from Fastlane to gplay CLI?▼

To migrate Android app metadata from Fastlane to gplay CLI, you can automate the conversion of Fastlane's directory structure into gplay's `listing.json` format while preserving text files, images, and changelogs. This streamlines the transition for Play Store release management.

Can I preview Fastlane to gplay metadata conversion before writing files?▼

Yes, you can preview Fastlane to gplay metadata conversion before writing files by using the dry-run option. This allows you to verify the generated `listing.json` structure and ensure assets map correctly without modifying your actual file system.

Does the gplay migration support converting specific locales from Fastlane?▼

Yes, the gplay migration supports converting specific locales from Fastlane. You can selectively migrate individual locale directories instead of migrating the entire metadata set at once, providing flexibility during the transition.

What Fastlane metadata files are converted for the gplay CLI?▼

Fastlane metadata files like `title.txt` and `short_description.txt` are converted into gplay's `listing.json` format. The migration also preserves your existing image assets and changelog structures to maintain your Play Store listing integrity.

When should I use a migration tool to switch from Fastlane to gplay?▼

You should use a migration tool to switch from Fastlane to gplay when you have a mature Android app with established Play Store metadata and want to leverage gplay CLI features without manually recreating your directory structures and assets.