setup-fastlane_skill

This skill guides you through a one-time Fastlane setup to automate iOS builds, tests, and App Store releases.

9

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill greenstevester/fastlane-skill --skill setup-fastlane

SKILL.md4.1 KB

Overview

This skill sets up Fastlane to automate building, testing, and releasing iOS and macOS apps. It provides a one-time project configuration that yields ready-to-run lanes for test, beta (TestFlight), and release (App Store) workflows. The setup includes environment checks, Homebrew-based Fastlane installation, and sample Appfile/Fastfile templates tailored to your project.

How this skill works

The skill inspects your project for Xcode project/workspace files, bundle ID, and team ID, then generates fastlane/Appfile and fastlane/Fastfile with lanes for test, beta, and release. It validates required tools (Xcode CLI, Homebrew, fastlane) and guides you to install missing components. Optional steps fetch existing App Store metadata and screenshots into fastlane/metadata for local editing.

When to use it

You want repeatable, scriptable iOS/macOS build and release flows.
You need a simple way to run tests, upload to TestFlight, or submit to the App Store.
You are scripting CI/CD pipelines and require deterministic build steps.
You want to manage App Store metadata and screenshots in source control.
You need to quickly onboard a project to Fastlane with minimal configuration.

Best practices

Install Fastlane via Homebrew to avoid Ruby dependency conflicts from Bundler.
Confirm project scheme name and replace {{SCHEME}} in Fastfile before running lanes.
Store fastlane configuration and metadata in your repository for traceability.
Use increment_build_number and explicit export_method in lanes to ensure reproducible builds.
If you hit code signing issues, enable or configure match (Fastlane’s code signing helper) rather than manual fixes.

Example use cases

Local developer runs fastlane ios test to validate changes before pushing.
Release manager runs fastlane ios beta to upload a new build to TestFlight for QA.
Automation pipeline invokes fastlane ios release to build and deliver a submission to the App Store.
Team stores app descriptions and screenshots in fastlane/metadata and updates them before release.
CI job runs fastlane lanes after successful unit tests to automate deployment.

FAQ

Ensure Xcode command line tools, Homebrew, and fastlane are installed. The setup script checks each and gives commands to install missing tools.

How do I set the app scheme and identifiers?

Replace placeholders in fastlane/Appfile and fastlane/Fastfile: set app_identifier, apple_id, team_id, and update the scheme name ({{SCHEME}}) to your app’s scheme.

Can I fetch my current App Store metadata?

Yes. Run fastlane deliver download_metadata and fastlane deliver download_screenshots to populate fastlane/metadata for editing and version control.