asc-release-flow

Determine App Store submission readiness and guide ASC release workflows.

103|6|Updated Aug 2, 2025
One-click install
npx skills add https://github.com/n0an/VivaDicta --skill asc-release-flow-n0an
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-release-flow
Source: https://github.com/n0an/VivaDicta/tree/main/.claude/skills/asc-release-flow
Command: npx skills add https://github.com/n0an/VivaDicta --skill asc-release-flow-n0an

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine whether an app is ready to submit and navigate the App Store release flow with asc, including first-time submission fixes for availability, in-app purchases, subscriptions, Game Center, and App Privacy.

Core Features & Use Cases

  • End-to-end readiness assessment using preflight checks.
  • Guided release flow: stage, run, and final submission with metadata, IAPs, subscriptions, Game Center, and App Privacy.
  • Fallbacks and advanced paths for API-based and web-session-assisted submissions.

Quick Start

Start with a preflight to verify readiness, then perform a staged release followed by the final submission using your app ID, version, and build IDs.

Frequently Asked Questions about asc-release-flow

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

FAQPage Schema
How do I check if my app is ready for App Store submission?

App Store submission readiness is determined by running preflight checks. This assesses metadata, in-app purchases, subscriptions, Game Center, and App Privacy to identify any blockers before you stage and run the release flow.

Can I use an API to automate the App Store release flow for a first-time submission?

Yes, the App Store release flow supports API commands for staging and running releases. For first-time submissions, it also provides experimental web-session escape hatches to handle initial setup and availability fixes.

What do I need to run a staged App Store release using ASC?

To run a staged App Store release, you must provide credentials, app IDs, version numbers, and build IDs. These identifiers allow the workflow to validate metadata and execute the submission process.

How do I fix blockers for in-app purchases and subscriptions during the release flow?

Blockers for in-app purchases and subscriptions are addressed during the guided release flow. The workflow validates IAP and subscription metadata, ensuring compliance before proceeding to the final App Store submission.

What is the best way to handle Game Center and App Privacy requirements for submission?

Game Center and App Privacy requirements are handled through guided metadata validation within the release workflow. This ensures your app meets all necessary privacy and Game Center configuration standards before submission.

Does the App Store release flow support web-session fallbacks when API limits are hit?

Yes, the release flow includes experimental web-session escape hatches as fallbacks. These are specifically useful for navigating first-time submission scenarios where standard API-based automation might be restricted.