mobile-cicd-generator_skill

This skill generates cross-platform mobile CI/CD pipelines for iOS and Android, including code signing, beta distribution, and crash reporting.
  • Python

5

GitHub Stars

2

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 williamzujkowski/cognitive-toolworks --skill mobile-cicd-generator

  • CHANGELOG.md1.5 KB
  • SKILL.md16.3 KB

Overview

This skill generates complete mobile CI/CD pipelines for iOS and Android, including build, code signing, beta distribution, and crash reporting. It produces ready-to-use CI YAML, Fastlane and Gradle snippets, and a secrets checklist to bootstrap reliable mobile DevOps across projects. The output targets common CI systems like GitHub Actions and GitLab CI and supports React Native and Flutter multi-platform flows.

How this skill works

The skill inspects the target platform (ios, android, react-native, flutter) and the chosen CI provider, then emits a CI workflow tailored to runner OS, caching, and build commands. If requested, it adds signing steps (Fastlane Match or manual keystore handling), beta distribution steps (TestFlight, Firebase, Play internal), and optional crash symbol uploads (Sentry, Crashlytics). It validates required credentials and returns a secrets checklist with instructions.

When to use it

  • Bootstrapping CI/CD for a new iOS, Android, React Native, or Flutter app
  • Automating code signing and consistent certificate handling across team members
  • Setting up automated beta distribution to TestFlight, Firebase App Distribution, or Play internal
  • Adding automated symbol uploads for crash reporting (Sentry, Crashlytics)
  • Standardizing repeatable pipeline templates across repositories

Best practices

  • Default to fastlane match for iOS team signing; store encrypted match repo and MATCH_PASSWORD as a secret
  • Keep Android keystore and passwords in CI secrets; never commit keystore files to source control
  • Pin Fastlane and Android Gradle Plugin versions and include lockfiles to ensure reproducible builds
  • Cache CocoaPods, Gradle, and npm artifacts and run iOS and Android jobs in parallel when possible
  • Never emit raw secrets in CI YAML; use provider secret placeholders like ${{ secrets.NAME }}

Example use cases

  • React Native app: generate dual GitHub Actions jobs for macOS (iOS) and Ubuntu (Android) with Fastlane Match and Firebase distribution
  • Flutter project: produce GitLab CI YAML that runs unit tests, builds Android AAB and iOS archive, and uploads artifacts
  • Android-only app: generate Gradle signing snippet and CI steps to assembleRelease and upload to Play internal via service account
  • iOS-only app: create Fastfile lanes for beta and release, plus TestFlight upload and dSYM upload to Sentry
  • Full release pipeline: automate version bump, changelog generation, staged Play/iOS release, and Crashlytics symbol uploads

FAQ

The skill halts signing/distribution steps and returns a secrets checklist with required credential names and where to store them in the CI provider.

Which signing method is used by default?

For iOS the default is fastlane match; for Android the default is manual keystore handling unless a managed flow is specified.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
mobile-cicd-generator skill by williamzujkowski/cognitive-toolworks | VeilStrat