From Build Swift Apps
Manages Xcode version/build numbers, archives, exports, uploads, and publishes IPA/PKG artifacts for TestFlight or App Store submission using `asc xcode` commands.
How this skill is triggered — by the user, by Claude, or both
Slash command
/build-swift-apps:appstore-archive-uploaderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Prefer `asc xcode archive` and `asc xcode export` over raw `xcodebuild` when they fit.
Prefer asc xcode archive and asc xcode export over raw xcodebuild when they fit.
Xcode/CLT installed; signing identity/profiles or automatic signing available; ASC auth configured for upload/build lookup.
asc xcode version view
asc xcode version edit --version "1.3.0" --build-number "42"
asc xcode version bump --type build
asc xcode version bump --type patch
asc builds next-build-number --app "APP_ID" --version "1.2.3" --platform IOS --output json
asc xcode version edit --build-number "NEXT_BUILD"
Use --project-dir, --project, and --target for multi-project/target determinism.
asc xcode archive --workspace "App.xcworkspace" --scheme "App" --configuration Release \
--clean --archive-path ".asc/artifacts/App.xcarchive" \
--xcodebuild-flag=-destination --xcodebuild-flag=generic/platform=iOS --output json
asc xcode export --archive-path ".asc/artifacts/App.xcarchive" \
--export-options "ExportOptions.plist" --ipa-path ".asc/artifacts/App.ipa" \
--xcodebuild-flag=-allowProvisioningUpdates --output json
Use --project "App.xcodeproj" for project-only apps. Add --wait to export/upload/publish when the next step depends on processed builds.
Upload/distribute:
asc builds upload --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --wait
asc publish testflight --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --group "GROUP_ID" --wait
asc publish appstore --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --version "1.2.3" --wait
asc publish appstore --app "APP_ID" --ipa ".asc/artifacts/App.ipa" --version "1.2.3" --wait --submit --confirm
asc xcode archive --project "MacApp.xcodeproj" --scheme "MacApp" --configuration Release \
--clean --archive-path ".asc/artifacts/MacApp.xcarchive" \
--xcodebuild-flag=-destination --xcodebuild-flag=generic/platform=macOS --output json
xcodebuild -exportArchive -archivePath ".asc/artifacts/MacApp.xcarchive" \
-exportPath ".asc/artifacts/MacAppExport" -exportOptionsPlist "ExportOptions.plist" \
-allowProvisioningUpdates
asc builds upload --app "APP_ID" --pkg ".asc/artifacts/MacAppExport/MacApp.pkg" \
--version "1.0.0" --build-number "123" --wait
PKG uploads require explicit --version and --build-number.
xcodebuild only when asc xcode archive/export --help cannot cover an option; try --xcodebuild-flag first.--xcodebuild-flag=-allowProvisioningUpdates, verify Xcode account/profiles, or use appstore-signing-setup.asc builds next-build-number, edit, rebuild, upload.--overwrite only when intentionally replacing local artifacts.appstore-review-readiness.npx claudepluginhub xopoko/plug-n-skills --plugin build-swift-appsManages Xcode version/build numbers, archives, exports, uploads, and publishes IPA/PKG artifacts for TestFlight or App Store submission using `asc xcode` commands.
App build, code signing, TestFlight, and App Store distribution for all Apple platforms. Use when preparing releases, configuring signing, uploading to TestFlight, or submitting to App Store.
Automates iOS/macOS app deployment to App Store Connect using asc CLI: TestFlight builds, App Store submissions, metadata/screenshots uploads, certificates/profiles management, review status checks, and Xcode Cloud workflows.