Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rorkai/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.
Passed 20 of 22 test cases with the skill, and 6 of 22 without it.
and 14 more in the full report
14 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to publish `.asc/artifacts/App.ipa` for App Store Connect app `987654321` version `1.2.3`, wait for processing, and automatically submit for review with confirmation. What is the CLI command?
| Checked | Without skill | With skill |
|---|---|---|
| Uses `asc publish appstore` with auto-submit and confirm options enabled. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
For a prepared xtool package on Linux, use portable iOS builds instead of the Xcode commands below. That workflow has a narrower project and signing contract.
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 in one command:
asc xcode version edit --next-build-number --app "APP_ID" --platform IOS --output json
Version mutations validate the full change before writing and return structured output identifying the configurations and files changed. The editor follows recursive xcconfig includes and preserves unrelated project and xcconfig content. Use asc builds next-build-number separately when you only want to inspect the remote-safe value without changing the project.
Version commands read project and xcconfig settings without launching Xcode. When those settings cannot resolve the version values, the default --xcodebuild-settings-lookup auto falls back to xcodebuild -showBuildSettings and warns on stderr. Use --xcodebuild-settings-lookup never in automation that must not launch Xcode implicitly.
Use asc xcode build for an ordinary simulator, device, or CI validation build. Provide exactly one project or workspace and a scheme.
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.