app-store-rejection-checker — скилл

---
name: app-store-rejection-checker
description: Audits an iOS or iPadOS Xcode project and its App Store Connect metadata against the current App Store Review Guidelines and reports likely rejection risks, each tied to a guideline number with evidence, a fix, and a confidence level. Use before an App Store submission, or when the user mentions App Store review, app rejection, review guidelines, rejection risk, submission preflight, or asks whether their app will pass review.
license: MIT
compatibility: Needs network access to fetch the live App Store Review Guidelines. Designed for repositories containing an Xcode project or Swift package.
metadata:
  author: dabodamjan
  homepage: https://github.com/dabodamjan/app-store-rejection-checker
allowed-tools: Read Grep Glob Bash WebFetch WebSearch
---

# App Store review preflight

Audit the repository and the developer's App Store Connect metadata the way an App Review
reviewer would: read the actual code, the actual configuration, and the actual store copy,
then report what is likely to be rejected and why.

Non-negotiable output rules:

1. Every finding cites a specific guideline number (or names the automated upload
   validation) and states the evidence found in this repository or metadata.
2. Every finding carries a confidence level (defined in Step 6). Never present a
   judgment call as a certainty.
3. Never promise approval, estimate approval odds as a percentage, or invent statistics.
   Passing this audit reduces known risks; it does not guarantee anything.
4. The live guidelines text fetched in Step 1 is the authority. The bundled reference
   files are a map of the rejection landscape (verified 2026-10-17); on any conflict,
   the live text wins, and the report should note the discrepancy. When the live fetch
   truncates before a section, a finding may quote wording recovered via the Step 1
   web-search fallback instead, labeled as a secondary source.

## Step 1: fetch the live guidelines

Do this before running any checklist.

Fetch https://developer.apple.com/app-store/review/guidelines/ with WebFetch. The page is
long and fetch results may truncate near the end (section 5.4 and later). Fetch results
are typically cached per URL, so fetching again retrieves the same snapshot; what a
targeted prompt changes is which part of that snapshot gets extracted. Use targeted
prompts to pull each area out of the snapshot:

1. Sections 1 and 2 (Safety, Performance): ask for the subsection structure and any
   wording relevant to the app under audit.
2. Sections 3 and 4 (Business, Design): same.
3. Section 5 (Legal): same. If the result cuts off before 5.4, re-prompting will not