Automate this: /mobile-release:preflight runs this audit against the real project and reports BLOCK/RISK/CLEAR with no uploads; --fix applies the repo-level fixes. It needs no credentials, which makes it the first thing to run in a session with no store access.

Decide whether pressing Submit for Review is safe, and say exactly what to change if it is not. Work through every section in order and give each a verdict of BLOCK, RISK, or CLEAR. Do not ask which sections to run — run them all, against the real project, using the commands given rather than by reading code and guessing.

Uploading the binary is the app-store-publish skill. Producing screenshots and preview videos is store-screenshots and store-preview-videos. This skill only decides whether the thing you already built will pass.

Confidence marks used throughout this skill and its references: [verified] — read off a primary vendor source on 2026-08-05. [snippet] — secondary source only, plausible but unconfirmed. [unverified] — not confirmed anywhere; check it before relying on it.

Review-readiness process:

Locate the app target's Info.plist, .xcodeproj/.xcworkspace, entitlements, and PrivacyInfo.xcprivacy. Everything below reads from these paths.
Run the sweep in 1. Checks you can run. Record each result; do not summarise from memory.
Check assets and metadata against 2; full tables in references/metadata-limits.md.
Check privacy against 3; reason codes and the SDK list in references/privacy.md.
Check guideline exposure — 4, expanded in references/guidelines.md.
Draft the App Review notes — 5, templates in references/review-notes.md.
Sweep the preemptable rejections in references/rejections.md, then emit the verdict table in Output Format. A single BLOCK means do not submit.

app-store-review