Asc Build Lifecycle

If you're managing iOS builds in App Store Connect and tired of clicking through the web UI to check processing status or clean up old builds, this gives you the command line tools to do it properly. It handles the full lifecycle: finding the latest build for a version, checking if processing is done, expiring builds older than a certain threshold, and getting the next safe build number. The dry run flag on expiration is smart, and the end-to-end publish commands with wait flags mean you can actually script your entire TestFlight or App Store release flow without babysitting it. Just note that the raw upload command only prepares uploads, use the publish commands for complete workflows.

skills.sh installs: 1.2K
GitHub stars: 905
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add rudrankriyam/asc-skills --skill asc-build-lifecycle --agent claude-code

Installs into .claude/skills of the current project.

Files

asc build lifecycle

Use this skill to manage build state, processing, and retention.

Find the right build

Latest build:
- asc builds info --app "APP_ID" --latest --version "1.2.3" --platform IOS
Next safe build number:
- asc builds next-build-number --app "APP_ID" --version "1.2.3" --platform IOS
- The command scans the full processed-build history and in-flight uploads, then returns one greater than the highest positive numeric build number. Blank or non-numeric processed build numbers are skipped with a warning; if no usable number remains, it falls back to --initial-build-number.
Recent builds:
- asc builds list --app "APP_ID" --sort -uploadedDate --limit 10

Inspect processing state

asc builds info --build-id "BUILD_ID"
TestFlight state in one call: asc builds info --build-id "BUILD_ID" --include buildBetaDetail,betaAppReviewSubmission,betaGroups --output json. A build never submitted for beta review has no betaAppReviewSubmissions entry in included.

SKILL.md on GitHub