android-fastlane-setup_skill

Overview

This skill sets up Fastlane for Android projects to automate Play Store deployment with supply and capture Play Store screenshots with screengrab. It scaffolds Gemfile, fastlane/Appfile, Fastfile lanes for builds, screenshot capture, staged rollouts, metadata templates, and a Screengrabfile. The goal is a reproducible CI-friendly deployment and screenshot pipeline tied to a Play Store service account.

How this skill works

The setup installs Fastlane and screengrab via Bundler, creates the fastlane directory structure and metadata templates, and adds lanes for building APK/AAB, capturing screenshots, and uploading to Play Store tracks (internal, beta, production). It wires the Play Store service account JSON into Appfile and configures Screengrab to produce screenshots in the metadata layout supply expects. A .gitignore update keeps built artifacts out of source control while tracking metadata.

When to use it

• You need repeatable Play Store uploads from CI or locally
• You want automated screenshot capture for store listings
• You need staged rollouts, halt/increase rollout controls
• You want a single repo-driven source for metadata and assets
• You're preparing CI/CD for Android releases

Best practices

• Install Ruby 2.7+ and use a Ruby version manager (rbenv/rvm)
• Keep service account JSON out of git and reference it via ENV var PLAY_STORE_SERVICE_ACCOUNT
• Run bundle install and use bundle exec fastlane to ensure consistent gems
• Store metadata and screenshots in fastlane/metadata and commit them to track store copy and assets
• Test lanes locally (bundle exec fastlane lanes) before wiring CI/Actions

Example use cases

• Capture screenshots via screengrab during CI and upload them with upload_screenshots lane
• Run release_internal to produce screenshots, build, and publish to internal track for QA
• Use release_beta with rollout option for staged beta releases
• Use increase_rollout or halt_rollout lanes to manage production rollouts without uploading new artifacts
• Run upload_metadata to update store text without rebuilding binaries