asc-release-flow

Orchestrates App Store releases with asc, from staging builds to review submission.

70|4|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/AlexW00/Zettel --skill asc-release-flow-alexw00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-release-flow
Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/asc-release-flow
Command: npx skills add https://github.com/AlexW00/Zettel --skill asc-release-flow-alexw00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating an App Store release involves many error-prone steps: staging metadata, attaching builds, validating readiness, uploading IPAs, and assembling multi-item review submissions. This Skill turns that into a guided, gated workflow with dry-run previews and confirmation requirements so releases do not fail halfway or create duplicate submissions. ## Core Features & Use Cases - Release lane selection: Choose between staging an existing build, submitting a prepared version, publishing from an IPA or local Xcode build, or assembling a multi-item review submission. - Readiness gate: Run asc validation with optional strict mode, and route Game Center, IAP, or other blockers to the correct remediation flow before submitting. - Multi-item submissions: Assemble review submissions containing the app version plus IAP, subscription, subscription-group, and Game Center version items, with duplicate-submission protection. - Use Case: You have a new 1.2.3 build processed in App Store Connect and want to ship it with a new subscription. Use this Skill to stage metadata, validate readiness, assemble the submission with both items, and submit after a confirmed dry run. ## Quick Start Ask the assistant to stage and submit App Store version 1.2.3 with the attached build using the asc release flow, starting with a dry run.

Frequently Asked Questions about asc-release-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit an app version to App Store review with asc?▼

Use asc review submit with the app ID, version, and build ID after metadata, review details, and product readiness are resolved. Run it with --dry-run first to preview the plan, then repeat with --confirm to execute the submission.

How do I attach an existing build to an App Store version?▼

Use asc release stage with the app ID, version string, and build ID. It ensures the version exists, applies or copies metadata, attaches the build, and runs validation without creating a review submission.

Can I submit IAP or Game Center items together with an app version?▼

Yes, assemble a multi-item review submission using asc review submissions-create and asc review items add with item types like inAppPurchaseVersions, subscriptionVersions, and gameCenterLeaderboardVersions. Inspect existing drafts first to avoid creating duplicate submissions.

What happens when asc validation reports blockers before submission?▼

Game Center item blockers are prepared within this flow using the multi-item reference, while IAP, subscription, and other validation failures are handed off to asc-submission-health. The release stops at the failing gate rather than producing a partial release.

Does asc publish appstore support building from a local Xcode project?▼

Yes, provide --workspace or --project with --scheme instead of --ipa to build locally before uploading. Add --submit to continue to review submission, or omit it for upload and build attachment only.