asc-release-flow

Determines App Store submission readiness and executes asc release workflows for iOS teams.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/pyronaur/ngents --skill asc-release-flow-pyronaur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-release-flow
Source: https://github.com/pyronaur/ngents/tree/main/docs/topics/apple/asc-cli/asc-release-flow
Command: npx skills add https://github.com/pyronaur/ngents --skill asc-release-flow-pyronaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine whether an app is ready to submit, then drive 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

  • Readiness checks using asc preflight to surface blockers and guidance for next steps.
  • Guided staging and full-release paths with asc release stage and asc release run to reach a complete submission.
  • First-time submission blockers handling for availability bootstrap, subscriptions, IAP, Game Center, and App Privacy with built-in fallbacks.
  • Lower-level control for advanced workflows via attach-build, review, and submission commands.
  • Coherent orchestration of app version metadata, builds, and submission items across the release lifecycle.

Quick Start

Provide a ready-to-submit assessment and execute the asc release flow for my app with the given 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 iOS app is ready for App Store submission?

App Store submission readiness is determined by running preflight checks to surface blockers and validate version metadata, build attachments, and credential readiness for iOS releases.

What is the best way to automate the iOS App Store release flow?

Automating the iOS App Store release flow involves orchestrating staging and full-release paths to drive app version metadata, builds, and submission items to a complete submission.

How do I handle first-time App Store submission blockers for IAPs and Game Center?

First-time App Store submission blockers for IAPs, subscriptions, and Game Center are handled by executing availability bootstrap, App Privacy fixes, and built-in fallbacks.

Can I attach a build to an App Store version manually during the release workflow?

Yes, you can attach a build to an App Store version manually using lower-level control commands for advanced workflows, alongside review and submission actions.

Why does my first-time app submission require a web-session bootstrap?

A web-session bootstrap is required for first-time app submission edge cases to satisfy availability checks and credential readiness when standard automated submission flows encounter initial setup blockers.