gplay-migrate-fastlane

Migrate Android Fastlane metadata to gplay format with locale selection and dry-run.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill gplay-migrate-fastlane-hanamizuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gplay-migrate-fastlane
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/android-dev/skills/gplay-migrate-fastlane
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill gplay-migrate-fastlane-hanamizuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate Android Fastlane metadata to the gplay CLI format, enabling a smoother transition and automated deployment workflow.

Core Features & Use Cases

  • Converts existing fastlane/metadata/android structure into gplay-compatible listings.
  • Supports selective locale migration and a dry-run option to preview changes before applying.
  • Useful during Play Store workflow migrations when moving from Fastlane to gplay.

Quick Start

Run the migration to convert your fastlane/metadata/android into gplay format using the gplay migrate fastlane command.

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 Fastlane metadata to the gplay format?

To migrate Android Fastlane metadata to the gplay format, run the gplay migrate fastlane command on your fastlane/metadata/android directory. This converts your existing Fastlane structure into gplay-compatible Play Store listings.

Can I preview Fastlane metadata migration changes before applying them?

Yes, you can preview Fastlane metadata migration changes using the optional dry-run feature. This allows you to review the gplay format conversion output before actually applying any modifications to your target directory.

Does the gplay migration tool support selecting specific locales from Fastlane metadata?

Yes, the gplay migration tool supports selecting specific locales during the Fastlane metadata conversion. You can target individual locales within your fastlane/metadata/android layout for a partial migration.

What do I need to use the gplay migrate fastlane command?

To use the gplay migrate fastlane command, you need the gplay CLI installed and authenticated, read access to your source fastlane/metadata/android directory, and a specified output directory for the converted listings.

Why migrate from Fastlane to gplay for Android Play Store deployments?

Migrating from Fastlane to gplay enables a smoother transition to an automated deployment workflow. It converts your existing Fastlane metadata structure into gplay-compatible listings, facilitating Play Store workflow migrations.

What is the required directory layout for migrating Fastlane metadata to gplay?

The required directory layout for migrating Fastlane metadata to gplay is the standard fastlane/metadata/android structure. The migration process applies specifically to projects using this layout to generate gplay-compatible output.