Agent skill

asc-xcode-build

Build, archive, generate export options, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.

rorkai948★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rorkai/app-store-connect-cli-skills --skill asc-xcode-build --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/asc-xcode-build/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 948
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Xcode build and export Use this skill when you need to build an app from source and prepare it for App Store Connect. Prefer `asc xcode archive` and `asc xcode export` over raw `xcodebuild` recipes when they fit the project. ## Preconditions - Xcode and command line tools are installed. - Signing identity and provisioning profiles are available, or automatic signing is enabled. - App Store Connect auth is configured when upload or build lookup is needed. ## Manage version and build numbers ```bash asc xcode version view asc xcode version edit --version "1.3.0" --build-number "42" asc xcode version edit --next-build-number --app "APP_ID" --platform IOS asc xcode version bump --type build asc xcode version bump --type patch asc xcode version bump --type build --next-build-number --app "APP_ID" --platform IOS ``` Use `--project-dir "./MyApp"` when not running from the project root. Use `--project "./MyApp/App.xcodeproj"` when the directory contains multiple projects. Use `--target "App"` and `--configuration "Release"` for deterministic reads and writes in multi-target or multi-configuration projects. To avoid low build-number rejects, resolve and apply the remote-safe build number

What's inside
Steps it walks through
  1. Preconditions
  2. Manage version and build numbers
  3. Preferred iOS/tvOS/visionOS build flow
  4. 1. Archive with asc
  5. 2. Export with asc
  6. 3. Upload or publish
  7. macOS App Store flow
  8. Raw xcodebuild fallback
  9. Troubleshooting
  10. No profiles for bundle ID during export
  11. CFBundleVersion too low
  12. Build rejected for missing macOS icon
  13. Notes
Commands it runs
asc xcode version view
asc xcode version edit --version "1.3.0" --build-number "42"
asc xcode version edit --next-build-number --app "APP_ID" --platform IOS
asc xcode version bump --type build
asc xcode version bump --type patch
asc xcode version bump --type build --next-build-number --app "APP_ID" --platform IOS
asc xcode version edit --next-build-number --app "APP_ID" --platform IOS --output json
asc xcode archive \
asc xcode export \
asc xcode export-options generate \
More from app-store-connect-cli-skills
All skills →
About this skill
What does the asc-xcode-build skill do?

Build, archive, generate export options, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.

How do I install it?

Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-xcode-build --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rorkai/app-store-connect-cli-skills, a repository with 948 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going