asc-submission-health

Diagnose App Store submission blockers and manage review status with the asc CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? App Store submissions fail or stall for opaque reasons, and developers struggle to identify which blocker is stopping a release, how to repair it, and whether to monitor, cancel, or retry an existing review submission. ## Core Features & Use Cases - Readiness Diagnosis: Runs asc validate and asc review doctor to produce an ordered blocker report covering builds, metadata, screenshots, encryption, age rating, and availability. - Repair Routing: Directs each blocker to the correct fix path, separating public App Store Connect API repairs from web-session automation and manual App Store Connect work. - Review Lifecycle Management: Monitors review status and history, cancels unhealthy submissions with confirmation, and decides when a repaired version is ready to hand back to the release flow. - Use Case: Your iOS app version is stuck and asc validate reports an unresolved encryption declaration plus a missing privacy policy URL. The skill identifies both blockers, walks you through the exact asc commands to fix them, and confirms when the version is ready to resubmit. ## Quick Start Ask the assistant to diagnose why your App Store version cannot be submitted and list the blocking issues with their repair steps.

Frequently Asked Questions about asc-submission-health

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

FAQPage Schema
How do I diagnose why my App Store submission is blocked?▼

Run asc validate with your app ID, version, and platform to get an ordered readiness report, then run asc review doctor for a review-specific explanation. Each blocker includes evidence and a routed repair path through the public API, web session, or manual App Store Connect work.

How do I check App Store review status from the command line?▼

Use asc review status with the app ID and version when the submission ID is unknown, or asc submit status with an exact submission or version ID. The asc review history command distinguishes a current stall from earlier rejected or completed submissions.

When should I cancel an App Store review submission?▼

Cancel only when the active submission is confirmed unhealthy and must be withdrawn, not merely because review is slow. Resolve the exact submission with asc submit status first, then run asc submit cancel with the --confirm flag after verifying state and user intent.

Can the App Store Connect API handle App Privacy and first-review IAP attachment?▼

No, the public API does not cover the full App Privacy workflow or first-review subscription and IAP attachment. These gaps require authenticated web-session commands like asc web privacy publish or asc web review iaps attach, with manual App Store Connect steps as fallback.

What makes an app version ready for App Store submission?▼

A version is ready when asc validate reports no blocking issues, the attached build is VALID, metadata, screenshots, review details, encryption, age rating, pricing, and availability are resolved, and IAP or subscription validators pass. A single successful validator exit is not sufficient proof.