asc-release-flow
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# App Store release orchestration Use this skill to carry a release from an approved plan to App Store review. Keep Game Center item preparation here; keep other blocker diagnosis and review recovery in `asc-submission-health`. ## Ownership boundary This skill owns: - staging metadata and attaching a build; - publishing an IPA or building locally; - submitting a prepared version; - assembling a multi-item review submission. Use [the preparation section](references/multi-item-submissions.md#prepare-every-item) for Game Center item preparation or attachment blockers. Use that reference's assembly and submission sections only after the app version is staged and the multi-item lane is selected. Stop and use `asc-submission-health` for other validation blockers, a stuck submission, cancellation, or retry decisions. ## Preconditions - Resolve `APP_ID`, the version string, `VERSION_ID` when needed, and `BUILD_ID` when a build already exists. - Configure auth with `asc auth login` or `ASC_*` environment variables. - Confirm the intended platform. Use `IOS` unless the app targets another platform. - Keep canonical metadata in `./metadata` when the workflow applies metadata. - Require a dry
- Ownership boundary
- Preconditions
- Choose the release lane
- Run the readiness gate
- Stage an existing build
- Submit a prepared version
- Upload or build, then publish
- Submit multiple review items
- Handoff after submission
- Guardrails
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table asc validate --app "APP_ID" --version "1.2.3" --platform IOS --strict --output table asc release stage \ asc review submit --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --dry-run --output table asc review submit --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --confirm asc publish appstore \
What does the asc-release-flow skill do?
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.
How do I install it?
Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rorkai/app-store-connect-cli-skills, a repository with 948 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.