Asc Build Lifecycle

This handles the full lifecycle of App Store Connect builds after they've been uploaded. You can track processing status, find the latest build for a version, figure out the next safe build number to use, and clean up old builds with expiration rules. The cleanup commands include a dry run mode, which is always nice to see before you delete things. It explicitly steers you away from basic upload commands toward the full publish flows in asc, which makes sense since you usually want the whole pipeline anyway. Good for CI systems that need to wait on processing or maintain build retention policies without manual pruning.

skills.sh installs: 7.6K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add rorkai/app-store-connect-cli-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