Skills

Asc Release Flow

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

Install

npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -g -a claude-code -y
Category
Mobile
Updated
9d ago
License
MIT
Context cost
Mediumabout 1,928 tokens
Runs scripts
No, instructions only

What it does

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.

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 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

Read the whole SKILL.md on GitHub

More in Mobile