ci-cd-setup
/ci-cd-setup
Generate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps. Use when setting up GitHub Actions, Xcode Cloud, or fastlane for continuous integration, TestFlight, or App Store deployment.
- Author
- rshankras ↗
- Repository
- claude-code-apple-skills ↗
- Licence
- MIT
- Last repository change
- 24.07.2026
Assessment and security
- Files in this package
- 12
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 4
No signals detected. Repository changed on 24.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: templates/xcode-cloud/ci_post_clone.sh, templates/xcode-cloud/ci_pre_xcodebuild.sh
What it does and when to use it
Generate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps. Use when setting up GitHub Actions, Xcode Cloud, or fastlane for continuous integration, TestFlight, or App Store deployment.
Original author description
Generate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps. Use when setting up GitHub Actions, Xcode Cloud, or fastlane for continuous integration, TestFlight, or App Store deployment.
How it works
- When This Skill Activates
- Pre-Generation Checks
- Configuration Questions
- Generated Files
- Merging Skill Rule Fragments
- Integration Steps
- Best Practices
- References
SKILL.md preview
---
name: ci-cd-setup
description: Generate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps. Use when setting up GitHub Actions, Xcode Cloud, or fastlane for continuous integration, TestFlight, or App Store deployment.
allowed-tools: [Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion]
last_verified: 2026-07-16
review_by: 2027-06-22
---
# CI/CD Setup Generator
Generate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps.
## When This Skill Activates
- User wants to automate their build and test process
- User mentions GitHub Actions, Xcode Cloud, or fastlane
- User wants to set up TestFlight or App Store deployment
- User asks about continuous integration for their app
## Pre-Generation Checks
Before generating, verify:
1. **Existing CI Configuration**
```bash
# Check for existing CI files
ls -la .github/workflows/ 2>/dev/null
ls -la ci_scripts/ 2>/dev/null
ls -la fastlane/ 2>/dev/null
```
2. **Project Structure**
```bash
# Find Xcode project/workspace
find . -name "*.xcodeproj" -o -name "*.xcworkspace" | head -5
```
3. **Package Manager**
```bash
# Check for SPM vs CocoaPods
ls Package.swift 2>/dev/null
ls Podfile 2>/dev/null
```
## Configuration Questions
### 1. CI/CD Platform
- **GitHub Actions** (Recommended) - Full control, extensive marketplace
- **Xcode Cloud** - Native Apple integration, simpler setup
- **Both** - GitHub for PRs/tests, Xcode Cloud for releases
### 2. Distribution Method
- **TestFlight** - Beta testing via App Store Connect
- **App Store** - Production releases
- **Direct** (macOS only) - Notarized DMG/PKG distribution
- **All** - Full pipeline from dev to production
### 3. Include fastlane?
- **Yes** - Advanced automation, match for code signing
- **No** - Simpler setup using xcodebuild directly
### 4. Code Signing Approach
- **Manual** - Certificates in GitHub Secrets
- **match** (fastlane) - Git-based certificate management
- **Xcode Cloud Managed** - Apple handles signing
## Generated Files
### GitHub Actions
```
.github/workflows/
├── build-test.yml # PR checks, unit tests
├── deploy-testflight.yml # TestFlight deployment
└── deploy-appstore.yml # App Store submission
```
### Xcode Cloud
```
ci_scripts/
├── ci_post_clone.sh # Post-clone setup
└── ci_pre_xcodebuild.sh # Pre-build configuration
```
### fastlane
```
fastlane/
├── Fastfile # Lane definitions
├── Appfile # App configuration
└── Matchfile # Code signing (if using match)
```
### SwiftLint
```
.swiftlint.yml # from templates/swiftlint/swiftlint.yml
```
## Merging Skill Rule Fragments
Skills in this library may ship graduated enforcement as a
`rules/swiftlint.yml` fragment (`opt_in_rules` + `custom_rules`) — prose
rules turned into deterministic lint. When generating `.swiftlint.yml`:
1. Start from `templates/swiftlint/swiftlint.yml`.
2. For each skill the project actually uses, check for
`skills/<category>/<skill>/rules/swiftlint.yml`; append its
`custom_rules` entries and union its `opt_in_rules`.
3. Respect fragment scoping comments — e.g. `observable_object_legacy`
applies only to iOS 17+/macOS 14+ deployment targets, and
`xctest_in_unit_tests` must keep its UITests exclusion (XCUITest
legitimately requires XCTest).
4. The generated `build-test.yml` runs the `lint` job automatically once
`.swiftlint.yml` exists (`if: hashFiles('.swiftlint.yml') != ''`).
Current fragments: `security/` (hardcoded secrets), `ios/coding-best-practices`
(print-in-production, legacy ObservableObject, force_unwrapping/force_try),
`testing/tdd-feature` (XCTest scoped out of unit tests),
`swift/concurrency` (@unchecked Sendable without justification).
## Integration Steps
### GitHub Actions Setup
1. **Add Repository Secrets** (Settings > Secrets and variables > Actions):
- `APP_STORE_CONNECT_API_KEY_ID` - API Key ID
- `APP_STORE_CONNECT_API_ISSUER_ID` - Issuer ID
- `APP_STORE_CONNECT_API_KEY_CONTENT` - Private key (.p8 content)
- `CERTIFICATE_P12` - Base64-encoded .p12 certificate
- `CERTIFICATE_PASSWORD` - Certificate password
- `PROVISIONING_PROFILE` - Base64-encoded provisioning profile
2. **Create App Store Connect API Key**:
- Go to App Store Connect > Users and Access > Keys
- Generate API Key with "App Manager" role
- Download the .p8 file (only available once)
3. **Export Certificate**:
```bash
# Export from Keychain as .p12, then base64 encode
base64 -i certificate.p12 | pbcopy
```
### Xcode Cloud Setup
1. **Enable Xcode Cloud** in Xcode:
- Product > Xcode Cloud > Create Workflow
- Connect to App Store Connect
2. **Configure Workflow**:
- Set start conditions (branch, PR, tag)
- Configure environment variables
- Set up post-actions (TestFlight, App Store)
3. **Add ci_scripts** to repository for customization
### fastlane Setup
1. **Install fastlane**:
```bash
brew install fastlane
```
2. **Initialize** (if starting fresh):
```bash
fastlane init
```
3. **Set up match** (optional, for code signing):
```bash
fastlane match init
fastlane match development
fastlane match appstore
```
## Best Practices
### Caching
- Cache Swift Package Manager dependencies
- Cache DerivedData for faster builds
- Use selective caching to avoid stale artifacts
### Secrets Management
- Never commit certificates or keys
- Use environment variables for sensitive data
- Rotate API keys periodically
### Build Optimization
- Use incremental builds where possible
- Parallelize test execution
- Skip unnecessary steps on draft PRs
### Notifications
- Slack/Discord integration for build status
- Email notifications for failures
- GitHub status checks for PRs
## References
- [GitHub Actions for Xcode](https://github.com/actions/runner-images/blob/main/images/macos)
- [Xcode Cloud Documentation](https://developer.apple.com/documentation/xcode/xcode-cloud)
- [fastlane Documentation](https://docs.fastlane.tools)
- [App Store Connect API](https://developer.apple.com/documentation/appstoreconnectapi)
Files in this package (12)
- SKILL.md 6 KB
- ci-cd-patterns.md 10 KB
- templates/fastlane/Appfile 2 KB
- templates/fastlane/Fastfile 7 KB
- templates/fastlane/Matchfile 3 KB
- templates/github-actions/build-test.yml 4 KB
- templates/github-actions/deploy-appstore.yml 7 KB
- templates/github-actions/deploy-testflight.yml 6 KB
- templates/swiftlint/swiftlint.yml 1 KB
- templates/xcode-cloud/XcodeCloudSetup.md 5 KB
- templates/xcode-cloud/ci_post_clone.sh 3 KB
- templates/xcode-cloud/ci_pre_xcodebuild.sh 3 KB
Versions
The database has no other skills named ci-cd-setup.
Database snapshot: 13.11.2026 · package version ffe89b74660a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100testflight-deploy
Set up automatic TestFlight deployment for iOS projects via Fastlane and GitHub Actions. Auto-detects project structure, generates CI/CD configuration files, and provides a step-by-step manual setup guide. Use when the user says "set up TestFlight", "configure CI/CD for iOS",… - 100fastlane
Automate mobile app builds, signing, and deployment with Fastlane — CI/CD for iOS and Android. Use when someone asks to "automate App Store deployment", "Fastlane", "automate iOS build", "CI/CD for mobile", "automate Play Store upload", "code signing automation", or "mobile… - 100mobile-cicd
Fastlane, GitHub Actions for mobile, code signing (iOS provisioning, Android keystores), beta distribution (TestFlight, Firebase App Distribution), and app store submissions. Use when setting up mobile build pipelines, automating releases, or managing signing. - 100fastlane-knowledge
Provides Fastlane configuration patterns for Flutter apps including iOS and Android lanes, code signing with match, CI/CD integration with GitHub Actions, and environment management. Use when user asks about Fastlane setup, deployment automation, code signing, or CI/CD for mobile. - 90mobile-deployment
Use this skill when the user asks about mobile app deployment, App Store, Play Store, TestFlight, Fastlane, code signing, mobile CI/CD, app release, or beta testing. - 100ios-release
Build, archive, and prepare iOS app for TestFlight/App Store. Handles version bumping, build number configuration, Xcode archiving, and upload. Use when preparing a new iOS release for TestFlight beta testing or App Store submission.