1. Habit
  2. Skills
  3. ASC Submission Health skill
rorkai · 8K installs

ASC Submission Health skill
Runs by itself, validation fails or stalls.

Submission blockers found and routed.

Install the ASC Submission Health skill and make it a habit: follow https://gethabit.dev/skills/rorkai/asc-submission-health.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

8K installs1K starsMIT licenceSource on GitHub ↗

ASC Submission Health

by rorkai · 8K installs

The skill

ASC submission health diagnoses App Store submission blockers with the asc CLI, routes repairs, monitors review status and decides when to cancel or retry.

Only when you ask.

The habit

Submission blockers found and routed.

↻ Runs by itselfvalidation fails or stalls

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

validation fails or stalls. Runs in Claude Code routine.

  • ↻ validation fails or stalls
  • asc validate reports blockers or review status unclear

02

It checks its work

validators clean, you confirm. If a check fails, it tells you.

  • ✓asc validate shows no blocking issues
  • ✓attached build is VALID
  • ✓asc validate iap or subscriptions show no blocking issues where relevant
  • ✓asc status --until review-done exits 0

03

It remembers

diagnosis log. The next run reads it first: last blockers found, repairs done and any SUBMISSION_ID.

loops/app-review-health-loop/log.md

One run, step by step.
Then it stops.

Stop ruleStops after one version per run, with at most one re-validation after repairs.

  1. 01

    Resolve the target

    Find APP_ID, version, BUILD_ID, platform and any SUBMISSION_ID, and stop if it is unclear.

  2. 02

    Diagnose

    Run asc validate and asc review doctor, then asc builds info and asc versions view for evidence.

  3. 03

    Route repairs

    Split blockers into public API, web-session and manual work, and fix one class at a time.

  4. 04

    Monitor review

    Use asc review status, asc submit status and asc review history to read the real state.

  5. 05

    Cancel only on yes

    Preview the submission, then run asc submit cancel with --confirm only after you agree.

  6. 06

    Hand back

    Re-run the validators and pass a healthy version to asc-release-flow for submission.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the ASC Submission Health skill helps.

Use it when

  • ✓ asc validate reports blockers
  • ✓ a version is not in a valid state
  • ✓ review status looks stuck

Skip it when

  • – uploading or submitting a healthy build
  • – you do not use the asc CLI

Questions

ASC Submission Health skill, answered.

Does it submit the app?

No. It hands healthy versions to asc-release-flow, which does the submission.

Will it cancel a slow review?

No. It cancels only with evidence and your approval, never just because review takes long.

How do I install the ASC Submission Health skill?

Copy the prompt at the top into your agent. It installs the skill from rorkai/app-store-connect-cli-skills and sets up the habit. Or run npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health.

Is the ASC Submission Health skill free?

Yes. It is published under MIT. Habit is free too.

ASC Submission Health. Now as a habit.

Install the ASC Submission Health skill and make it a habit: follow https://gethabit.dev/skills/rorkai/asc-submission-health.md

  • Free
  • No account
  • Undo in one line

All rorkai skills →More ops skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by rorkai, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.