CI CD Setup Skill for Claude

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.

14k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

585

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/rshankras/claude-code-apple-skills --skill ci-cd-setup

The instruction itself

24 sections, as written by the author

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:

Existing CI Configuration

   # 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

Project Structure

   # Find Xcode project/workspace
   find . -name "*.xcodeproj" -o -name "*.xcworkspace" | head -5

Package Manager

   # 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:

Start from templates/swiftlint/swiftlint.yml.
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.

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).

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

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

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)

Export Certificate:

   # Export from Keychain as .p12, then base64 encode
   base64 -i certificate.p12 | pbcopy

Xcode Cloud Setup

Enable Xcode Cloud in Xcode:
Product > Xcode Cloud > Create Workflow
Connect to App Store Connect

Configure Workflow:
Set start conditions (branch, PR, tag)
Configure environment variables
Set up post-actions (TestFlight, App Store)

Add ci_scripts to repository for customization

fastlane Setup

Install fastlane:

   brew install fastlane

Initialize (if starting fresh):

   fastlane init

Set up match (optional, for code signing):

   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

Other skills for the same job

different authors, same section of the catalogue

Azure Kubernetes Automatic Readiness

by microsoft

vendor ×3

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.

Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.

Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).

Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

17k tokens

How to use it

Copy the folder

Take rshankras/ci-cd-setup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference brew. Without those the skill loads but fails at the first command.