Asc Build Lifecycle
- 2.4k installs
- 934 repo stars
- Updated July 21, 2026
- rudrankriyam/app-store-connect-cli-skills
asc-build-lifecycle tracks asc build processing, publish flows, and expiration for iOS TestFlight and App Store.
About
The asc-build-lifecycle skill manages App Store Connect build state, processing waits, retention, and publish flows with the asc CLI. Finding builds uses asc builds info with latest and version platform filters, asc builds next-build-number for safe increments, and sorted asc builds list for recent uploads. Processing state is inspected per build-id before distribution. End-to-end publish prefers asc publish testflight with ipa, group, and wait flags or asc publish appstore with version, wait, submit, and confirm for store submission. Cleanup supports expire-all with older-than dry-run previews and confirmed expiration, plus single build expire by id. Notes clarify asc builds upload only prepares upload operations while asc publish handles full pipelines, and long processing should use wait, poll-interval, and timeout options. Teams invoke it when waiting on build processing, choosing build numbers, pushing IPAs to TestFlight or App Store, or pruning stale binaries to manage account retention limits.
- Find latest builds, next build numbers, and recent upload lists.
- Inspect per-build processing state before distribution.
- End-to-end asc publish for TestFlight and App Store with --wait.
- Expire-all dry-run and confirmed cleanup by age or single build.
- Prefer asc publish over builds upload for full distribution flows.
Asc Build Lifecycle by the numbers
- 2,359 all-time installs (skills.sh)
- +26 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #90 of 1,048 Mobile Development skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
asc-build-lifecycle capabilities & compatibility
- Capabilities
- latest and recent build discovery commands · processing state inspection per build id · testflight and app store publish with wait optio · bulk and single build expiration workflows · upload vs publish operational guidance
- Use cases
- devops · orchestration
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-build-lifecycleAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2.4k |
|---|---|
| repo stars | ★ 934 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 21, 2026 |
| Repository | rudrankriyam/app-store-connect-cli-skills ↗ |
How do I find the right build, wait for processing, publish IPAs, and clean up old asc builds?
Track iOS build processing, resolve latest builds, publish to TestFlight or App Store, and expire old builds with asc.
Who is it for?
iOS release engineers managing asc build state from upload through TestFlight or App Store.
Skip if: Skip for Android builds or TestFlight group management covered by sibling TestFlight skills.
When should I use this skill?
User asks asc builds info --latest, publish testflight, expire-all, or next-build-number.
What you get
Resolved build IDs, completed publish with wait flags, or expired stale builds after dry-run preview.
- build processing status
- next build number
- cleaned build list
By the numbers
- asc builds list supports --limit 10 for recent build history
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- Recent builds:
asc builds list --app "APP_ID" --sort -uploadedDate --limit 10
Inspect processing state
asc builds info --build-id "BUILD_ID"
Distribution flows
- Prefer end-to-end:
asc publish testflight --app "APP_ID" --ipa "./app.ipa" --group "GROUP_ID" --waitasc publish appstore --app "APP_ID" --ipa "./app.ipa" --version "1.2.3" --wait --submit --confirm
Cleanup
- Preview expiration:
asc builds expire-all --app "APP_ID" --older-than 90d --dry-run- Apply expiration:
asc builds expire-all --app "APP_ID" --older-than 90d --confirm- Single build:
asc builds expire --build-id "BUILD_ID" --confirm
Notes
asc builds uploadprepares upload operations only; useasc publishfor end-to-end flows.- For long processing times, use
--wait,--poll-interval, and--timeoutwhere supported.
Related skills
Xcode Project SetupAutomatically create and configure a new Xcode project with Swift Package Manager dependencies for iOS or macOS agent projects.71.4k387
Expo Tailwind SetupInstantly configure Tailwind CSS v4 with NativeWind v5 and react-native-css inside an Expo project for universal styling.45.6k2.3kExpo Dev ClientCreate custom development clients for Expo React Native apps that need native modules or Apple-specific targets.44.7k2.3k
Swiftui Expert SkillGet expert guidance when writing, reviewing, or refactoring SwiftUI views, state, performance, and modern iOS/macOS APIs.27.2k3.3k
Flutter Apply Architecture Best PracticesEnforce clean layered architecture when creating or refactoring a Flutter mobile application.25k2.7kFlutter Build Responsive LayoutGenerate Flutter layouts that automatically adapt to phones, tablets, and desktop screens using LayoutBuilder and MediaQuery.24.2k2.7kForks & variants (3)
Asc Build Lifecycle has 3 known copies in the catalog totaling 3.3k installs. They canonicalize to this original listing.
- rorkai - 2.1k installs
- rudrankriyam - 1.2k installs
- ehmo - 1 installs
How it compares
Use asc-build-lifecycle over manual App Store Connect UI when CI needs scripted build-number increments and processing polls via asc.
FAQ
upload vs publish?
asc builds upload prepares upload operations only; use asc publish for end-to-end TestFlight or App Store flows.
How do I wait on processing?
Use --wait, --poll-interval, and --timeout on publish or info commands where supported.
How do I safely delete old builds?
Run expire-all with --older-than and --dry-run first, then --confirm to apply or expire a single build by id.