asc-submission-health

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

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-submission-health-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-submission-health
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/asc-submission-health
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-submission-health-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? App Store submissions often fail or stall for unclear reasons, and developers struggle to identify which blocker is stopping a release. This Skill diagnoses readiness failures, routes each blocker to the correct repair path, and manages review monitoring, cancellation, and retry decisions using the asc CLI. ## Core Features & Use Cases - Readiness Diagnosis: Runs asc validate and asc review doctor to produce an ordered list of blockers with evidence, covering builds, metadata, screenshots, encryption, age rating, and availability. - Repair Routing: Separates public-API repairs from web-session and manual work, with dedicated references for readiness repairs, digital goods (IAP/subscriptions), and App Privacy. - Review Lifecycle Management: Monitors review status and history, cancels unhealthy submissions with confirmation, and decides when a repaired version can return to the release flow. - Use Case: Your asc validate run reports an invalid build state and a missing App Privacy publish confirmation. Use this Skill to identify each blocker, fix the encryption declaration via the public API, verify privacy state through the web-session flow, and hand the healthy version back to asc-release-flow. ## Quick Start Ask the agent to diagnose why my App Store version 1.2.3 cannot be submitted and list the blocking issues with the next repair command.

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 remediation plan, then run asc review doctor for a review-specific explanation. Each blocker is routed to a public-API repair, a web-session command, or a manual App Store Connect step.

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.

Does this skill submit apps to App Store review?▼

No, this skill only diagnoses blockers and manages existing submissions. Once a version passes validation with no blocking issues, it hands the healthy version back to asc-release-flow, which owns staging, upload, publication, and submission execution.

Can I validate in-app purchases and subscriptions before review?▼

Yes, run asc validate iap or asc validate subscriptions to check product readiness. The digital-goods reference covers preparing IAP and subscription versions, first-review attachment via web session, and handing version IDs to the release flow.

When should I cancel an App Store review submission?▼

Cancel only after confirming the exact active submission with asc submit status and getting user approval, using asc submit cancel with the --confirm flag. Do not cancel solely because review is taking longer than expected.

Does App Store Connect API cover App Privacy publishing?▼

No, the public API cannot confirm the full App Privacy publish state. The skill uses authenticated web-session commands like asc web privacy pull, plan, apply, and publish, with a manual App Store Connect check as fallback.