# Asc Release Flow

Orchestrate App Store releases with asc, including staging a version, uploading or...

- Repository: https://github.com/rorkai/app-store-connect-cli-skills (1119 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -g -a claude-code -y`
Codex: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -g -a codex -y`
Cursor: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -g -a cursor -y`
Gemini CLI: `npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add rorkai/app-store-connect-cli-skills`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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. Switch to `asc-submission-health` for other validation blockers, a stuck submission, cancellation, or retry decisions.

Switch skills within the current task, preserving resolved targets, authorization, and verified progress. A failing gate blocks dependent mutations, not diagnosis or independent authorized work. Continue authorized repairs and resume this flow; request new authority only when repairs exceed the agreed scope.

## 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 run before a mutating high-level command, then require `--confirm` for submission.

## Choose the release lane

The rest: https://github.com/rorkai/app-store-connect-cli-skills/blob/HEAD/skills/asc-release-flow/SKILL.md
