mcpbeat

Asc Build Lifecycle

rorkai/asc-build-lifecycle

Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.

340 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
946
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-build-lifecycle

The instruction itself

6 sections, as written by the author

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" --wait
  • asc 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 upload prepares upload operations only; use asc publish for end-to-end flows.
  • For long processing times, use --wait, --poll-interval, and --timeout where supported.

How to use it

Copy the folder

Take rorkai/asc-build-lifecycle from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.