awesome-mobile-release-agent-skills

Use Apple's phased release for automatic updates on iOS — behavior, pausing, resuming, and interaction with manual updates. Use this when shipping production iOS builds.

Use Play percentage rollouts and iOS phased release to limit blast radius. Use this when planning or operating a production release.

Generate keystores, enrol in Play App Signing, and understand v1/v2/v3/v4 APK signature schemes. Use this when setting up Android release signing.

Diagnose and fix common Apple and Google code-signing errors. Use this when a release build fails to sign, upload, or install.

Manage Apple certificates, provisioning profiles, automatic vs manual signing, and fastlane match. Use this when setting up iOS release signing.

Publish Android apps to Amazon Appstore, Huawei AppGallery, Samsung Galaxy Store, and deal with HMS vs GMS. Use this when targeting non-Google Android markets.

Release to the App Store using App Store Connect, TestFlight, metadata, and screenshots. Use this when shipping an iOS build to Apple.

Release to Google Play using internal/closed/open tracks, AAB uploads, and the Data Safety form. Use this when shipping an Android build to the Play Console.

Generate release notes from Conventional Commits with git-cliff, conventional-changelog, or release-please. Use this when automating the changelog and store release notes.

Apply SemVer to mobile apps — versionName, versionCode, CFBundleShortVersionString, CFBundleVersion, and release branching. Use this when bumping versions or designing branch strategy.

Choose between Bitrise and Codemagic — stack choice, workflows, caches, and secrets. Use this when you need managed macOS runners without maintaining your own.

Set up a complete Fastlane pipeline — Fastfile structure, lanes, match, pilot, supply. Use this when introducing Fastlane to an iOS or Android project.

Build and release mobile apps from GitHub Actions — macOS runners, AAB/IPA artifacts, signing secrets, and tag-triggered deploys. Use this when GitHub Actions is the CI of record.

Complete and maintain the Google Play Data Safety form accurately, aligned to shipped SDKs. Use this when launching, adding SDKs, or auditing data practices.

Declare iOS Required Reason APIs and tracking in PrivacyInfo.xcprivacy. Use this when adding SDKs, new APIs, or preparing for App Store submission.

Run a mobile hotfix — branches, cherry-picks, expedited review, and coordinated Play/App Store submission. Use this when a bug in production needs an urgent patch.

Halt rollouts, restore previous binaries, and use kill switches for server-side rollback. Use this when a production release is causing harm.

Define a crash-rate SLO, alert on it, and use breaches as automatic rollback triggers. Use this when formalising release health policy.

Monitor a mobile release — crash-free sessions SLO, adoption curve, ratings, and performance regressions. Use this during the first week after every release.

Decouple deploy from release using feature flags, kill switches, and remote config. Use this when shipping risky or incremental features.