asc-release-flow

Orchestrate App Store releases with asc from staging through review submission.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-release-flow-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-release-flow
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-release-flow
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-release-flow-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating an App Store release involves staging metadata, attaching builds, validating readiness, and submitting for review, and mistakes like duplicate submissions or unvalidated uploads can block a release. This Skill provides a guarded, lane-based workflow for driving a release from an approved plan to App Store review using the asc CLI. ## Core Features & Use Cases - Release lane selection: Choose between staging an existing build, submitting a prepared version, publishing an IPA or local build, or assembling a multi-item review submission. - Readiness gating: Run asc validation with optional strict mode, and route Game Center, IAP, or other blockers to the correct preparation or diagnosis flow before submitting. - Multi-item submissions: Assemble a single review submission containing the app version plus IAP, subscription, subscription-group, or Game Center version items, with dry-run and confirmation safeguards. - Use Case: You have build 42 processed and metadata ready in ./metadata for version 1.2.3. Use this Skill to dry-run the staging plan, confirm the mutation, validate the version, and submit it for App Store review without creating duplicate submissions. ## Quick Start Use the asc-release-flow skill to stage build BUILD_ID for app APP_ID version 1.2.3 with metadata from ./metadata, then submit it for App Store review after 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 iOS app for App Store review from the command line?▼

Use asc review submit with the app ID, version, and build ID after metadata, review details, and build processing 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 --app, --version, and --build to ensure the version, apply metadata from a directory or copy it from a previous version, attach the build, and run validation without creating a review submission.

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

Yes, create one review submission and add items with asc review items add using item types like inAppPurchaseVersions, subscriptionVersions, or gameCenterLeaderboardVersions. Prepare every item first and inspect the assembled draft before submitting.

What happens if App Store validation fails before submission?▼

The flow stops at the failing gate rather than producing a partial release. Game Center item blockers are handled by the preparation section, while other validation blockers, stuck submissions, or retry decisions are routed to asc-submission-health.

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

Yes, provide --workspace or --project with --scheme instead of --ipa to build locally, then upload and optionally submit. Add --metadata-dir to apply canonical version metadata and --wait to block until processing completes.