Run any Skill in Manus with one click

ios-auto-release

Stars0

Forks0

UpdatedFebruary 24, 2026 at 19:03

Manage the two-stage iOS release pipeline using GitHub Actions for CI/semantic versioning and Xcode Cloud for App Store distribution. Use when the user needs to (1) trigger a new iOS release, (2) understand or modify CI workflows (ios-ci.yml, ios-setup.yml, create-release.yaml), (3) debug version bumping or Xcode Cloud builds, (4) update the ci_post_clone.sh script, (5) configure or rotate CI secrets, (6) understand conventional commit conventions for version bumps, or (7) troubleshoot failed releases or TestFlight submissions.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rxtech-lab

rxtech-lab/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name

ios-auto-release

description

iOS Auto Release

Two-stage release pipeline: GitHub Actions for CI + semantic versioning, Xcode Cloud for App Store distribution.

Architecture

Push to main
     │
     ▼
GitHub Actions ──► Build + Test (5 parallel jobs)
     │
     ▼
Manual Trigger ──► Semantic Release ──► Analyzes commits
                        │
                        ▼
                  Creates git tag (v1.2.3)
                  Creates GitHub Release
                        │
                        ▼
              Xcode Cloud detects tag ──► ci_post_clone.sh
                        │                     │
                        │              Extracts version from CI_TAG
                        │              Stamps MARKETING_VERSION
                        │              Sets CURRENT_PROJECT_VERSION
                        │                     │
                        ▼                     ▼
                  Xcode Cloud builds ──► TestFlight / App Store

Release Workflow

Creating a release

Ensure all commits on main follow conventional commit format
Go to GitHub Actions → Create a new release workflow → Run workflow on main
Semantic Release analyzes commits since last tag and determines version bump
If releasable commits exist → creates git tag vX.Y.Z + GitHub Release with auto-generated notes
Xcode Cloud detects the tag → runs ci_post_clone.sh → builds and uploads to TestFlight

Conventional commit conventions

Prefix	Bump	Example
`fix:`	Patch (1.0.0 → 1.0.1)	`fix: resolve crash on item delete`
`feat:`	Minor (1.0.0 → 1.1.0)	`feat: add QR code scanning`
`feat!:` or `BREAKING CHANGE:`	Major (1.0.0 → 2.0.0)	`feat!: redesign API response format`
`chore:`, `docs:`, `ci:`	No release	`chore: update dependencies`

Version identifiers

Field	Build Setting	Example	Purpose
Version	`MARKETING_VERSION`	`1.2.3`	User-facing App Store version
Build	`CURRENT_PROJECT_VERSION`	`42`	Internal build number, auto-incremented by Xcode Cloud

Default values in project file (1.0 / 5) are overwritten at build time — versions are never committed to the repo.

File Reference

File	Purpose
`.github/workflows/ios-ci.yml`	CI on every push: 5 parallel build/test jobs
`.github/workflows/ios-setup.yml`	Reusable setup (secrets, tooling, backend, OpenAPI)
`.github/workflows/create-release.yaml`	Manual semantic release trigger
`.releaserc`	Semantic release plugin config
`RxStorage/ci_scripts/ci_post_clone.sh`	Xcode Cloud version bumping + environment setup
`scripts/ios-build.sh`	iOS simulator build
`scripts/ios-test.sh`	Swift Package unit tests
`scripts/ios-ui-test.sh`	UI tests with backend
`scripts/macos-build.sh`	macOS build
`scripts/ios-update-openapi.sh`	OpenAPI client regeneration
`scripts/decode-env-secrets.sh`	Decode base64 test secrets

References

GitHub Actions CI (workflow details, jobs, reusable setup): github-actions.md
Xcode Cloud (post-clone script, version bumping, environment variables): xcode-cloud.md
Secrets management (encoding, decoding, rotation for both CI systems): secrets.md

More from this repository

same repository

react-native-android-release

rxtech-lab/agent-skills

Set up and manage React Native (Expo/EAS) Android releases via GitHub Actions. Use when the user needs to (1) configure the Android release pipeline (local EAS build, version bump, Google Play submit), (2) create or modify the GitHub Actions release workflow (android-release.yml), (3) set up or debug eas.json build/submit profiles, (4) configure the Google Play service-account credential as a base64 secret, (5) wire EXPO_TOKEN and EAS-managed signing keystore, (6) bump app.json version from a release tag with EAS remote versionCode auto-increment, (7) publish an AAB to the Google Play internal track via EAS Submit, or (8) fall back to a bare React Native Gradle + Fastlane path when not using Expo managed workflow.

2026-06-020

macos-extensionkit

rxtech-lab/agent-skills

Build a macOS app that hosts its own in-app UI extension using Apple's ExtensionKit / ExtensionFoundation (AppExtension, AppExtensionPoint, EXHostViewController, NSXPC). Use when creating a host app + bundled app-extension target, defining a custom extension point, sharing an API/XPC contract core between host and extension, embedding extension SwiftUI inside the host, wiring bidirectional host↔extension messaging, or debugging extension discovery/activation failures (OSStatus -10814, "Failed to get extension process and XPC endpoints", LSRegisterURL -10819).

2026-06-020

argo-trading

rxtech-lab/agent-skills

Iterate on algorithmic trading strategies in ArgoTradingSwift (`.rxtrading` documents) via the embedded MCP server. Use when the user wants to write, build, backtest, or improve Go-based trading strategies that compile to WASM, load a `.wasm` strategy into the app, run a backtest against a schema/dataset, or analyze backtest results (stats.yaml + per-trade parquet). Triggers include phrases like "write a trading strategy", "backtest this strategy", "beat buy-and-hold", "load_strategy", "run_backtest", and any mention of argo-trading, ArgoTradingSwift, or `.rxtrading` files.

2026-04-190

sparkle-github-release

rxtech-lab/agent-skills

Set up and manage macOS app releases with Sparkle auto-update via GitHub Actions. Use when the user needs to (1) configure the macOS release pipeline (build, sign, notarize, distribute), (2) integrate Sparkle framework for auto-updates in a Swift macOS app, (3) create or modify the GitHub Actions release workflow (macos-release.yml), (4) generate or debug Sparkle appcast.xml feeds, (5) configure or rotate signing/notarization secrets, (6) set up GitHub Pages deployment for appcast hosting, (7) write or update CI scripts for code signing, notarization, or appcast generation, or (8) troubleshoot DMG creation, notarization failures, or Sparkle update issues.

2026-03-130

openapi-integration

rxtech-lab/agent-skills

Set up and maintain OpenAPI 3.0 integration between a Next.js backend and a Swift iOS client. Use when the user needs to (1) set up OpenAPI spec generation from Zod schemas using next-openapi-gen, (2) configure Swift OpenAPI generator for an iOS package, (3) create or update API routes with JSDoc annotations, (4) create Zod schemas for API contracts, (5) sync the OpenAPI spec between backend and iOS, (6) create Swift service layers wrapping generated API clients, or (7) troubleshoot OpenAPI generation or Swift type issues.

2026-02-070

skill-creator

rxtech-lab/agent-skills

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

2026-02-070

name

ios-auto-release

description

iOS Auto Release

Two-stage release pipeline: GitHub Actions for CI + semantic versioning, Xcode Cloud for App Store distribution.

Architecture

Push to main
     │
     ▼
GitHub Actions ──► Build + Test (5 parallel jobs)
     │
     ▼
Manual Trigger ──► Semantic Release ──► Analyzes commits
                        │
                        ▼
                  Creates git tag (v1.2.3)
                  Creates GitHub Release
                        │
                        ▼
              Xcode Cloud detects tag ──► ci_post_clone.sh
                        │                     │
                        │              Extracts version from CI_TAG
                        │              Stamps MARKETING_VERSION
                        │              Sets CURRENT_PROJECT_VERSION
                        │                     │
                        ▼                     ▼
                  Xcode Cloud builds ──► TestFlight / App Store

Release Workflow

Creating a release

Ensure all commits on main follow conventional commit format
Go to GitHub Actions → Create a new release workflow → Run workflow on main
Semantic Release analyzes commits since last tag and determines version bump
If releasable commits exist → creates git tag vX.Y.Z + GitHub Release with auto-generated notes
Xcode Cloud detects the tag → runs ci_post_clone.sh → builds and uploads to TestFlight

Conventional commit conventions

Prefix	Bump	Example
`fix:`	Patch (1.0.0 → 1.0.1)	`fix: resolve crash on item delete`
`feat:`	Minor (1.0.0 → 1.1.0)	`feat: add QR code scanning`
`feat!:` or `BREAKING CHANGE:`	Major (1.0.0 → 2.0.0)	`feat!: redesign API response format`
`chore:`, `docs:`, `ci:`	No release	`chore: update dependencies`

Version identifiers

Field	Build Setting	Example	Purpose
Version	`MARKETING_VERSION`	`1.2.3`	User-facing App Store version
Build	`CURRENT_PROJECT_VERSION`	`42`	Internal build number, auto-incremented by Xcode Cloud

Default values in project file (1.0 / 5) are overwritten at build time — versions are never committed to the repo.

File Reference

File	Purpose
`.github/workflows/ios-ci.yml`	CI on every push: 5 parallel build/test jobs
`.github/workflows/ios-setup.yml`	Reusable setup (secrets, tooling, backend, OpenAPI)
`.github/workflows/create-release.yaml`	Manual semantic release trigger
`.releaserc`	Semantic release plugin config
`RxStorage/ci_scripts/ci_post_clone.sh`	Xcode Cloud version bumping + environment setup
`scripts/ios-build.sh`	iOS simulator build
`scripts/ios-test.sh`	Swift Package unit tests
`scripts/ios-ui-test.sh`	UI tests with backend
`scripts/macos-build.sh`	macOS build
`scripts/ios-update-openapi.sh`	OpenAPI client regeneration
`scripts/decode-env-secrets.sh`	Decode base64 test secrets

References

GitHub Actions CI (workflow details, jobs, reusable setup): github-actions.md
Xcode Cloud (post-clone script, version bumping, environment variables): xcode-cloud.md
Secrets management (encoding, decoding, rotation for both CI systems): secrets.md