App Store Preflight skill
A skill that scans an iOS or macOS project for common App Store rejection patterns before you submit
- 1,416 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads project sources and metadata and may edit files when autofixing
- Runs the asc CLI, which talks to App Store Connect over the network
Install
- Works in
Manual install
npx skills add truongduy2611/app-store-preflight-skillsInstalls the skill into the agent's skills directory. Metadata checks additionally need the asc CLI (brew install asc).
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads project sources and metadata and may edit files when autofixing
- Runs the asc CLI, which talks to App Store Connect over the network
This is third-party code. Review the repository files before installing.
What it does
The skill runs a project against the rules Apple most often rejects apps for. It first identifies the app type and loads the matching checklist from references/guidelines, then uses the asc CLI to pull version metadata and check it by category: metadata, subscriptions and in-app purchases, privacy, design and entitlements. For each finding it reports a severity, the affected file and the fix, and after edits it re-runs the affected checks. All rules live in the repository as markdown files, each tied to an Apple guideline number.
Who it is for. For iOS and macOS developers preparing an app for App Store submission.
Good fit when
- You are about to submit an app and want to catch rejection reasons in advance
- Apple returned a rejection and you need to find what exactly is wrong
- You need an audit of metadata, subscriptions, privacy or entitlements before release
Not a fit when
- The project is not iOS or macOS
- You need to upload the build to the App Store rather than check it: the skill does not do that
Example request
Check my project for App Store rejection reasons before submission and show what to fixLimitations
Metadata checks rely on the asc CLI (brew install asc) and assume the canonical asc metadata pull layout; some examples need jq. The skill works with local sources and metadata and does not submit the build to the App Store. The rules reflect a snapshot of Apple's guidelines and do not guarantee approval.
How to disable. Remove the skill folder from the agent's skills directory (for example ~/.claude/skills/) or undo the install made via npx skills.
FAQ
Does the skill submit the app to the App Store?
No. It only checks the project and metadata and suggests fixes; you submit the app yourself.
What is needed for metadata checks?
The asc CLI (brew install asc) and metadata pulled via asc metadata pull in the canonical layout.
Discussion
No questions or reviews yet.
Related
SkillsClaude Code skill that audits an iOS app before App Store submission: guideline, code evidence, fix and confidence per finding.
An agent checks Apple app code against every App Store guideline and shows what could trigger a rejection before you submit
A Claude Code plugin that audits a mobile app against App Store and Google Play review rules before submission.
Claude Code skill that takes an iOS or Flutter app from archive and signing to App Store submission and review rejection recovery.
A guard hook before an App Store or Google Play submit finds critical rejection risks and blocks the command until they are fixed.
A CLI and Claude Code plugin that find App Store and Google Play rejection causes before you submit, citing the rule for each.
README in short
The README describes a skill that finds common Apple review guideline violations before an app is submitted. It works in steps: identify the app type and load a checklist, pull metadata via the asc CLI, check the rules by category, build a report with severity and fixes, apply edits and re-check. references holds an index of all guidelines and ten app-type checklists, plus rules for metadata, subscriptions, privacy, design and entitlements. The skill ties into the asc CLI and the related app-store-connect-cli-skills set. MIT licensed.
README badge
Original SKILL.md
--- name: app-store-preflight-skills description: > Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission. Use when preparing an app for App Store review, after receiving a rejection from Apple, or when auditing metadata, subscriptions, privacy manifests, entitlements, or design compliance. Integrates with the asc CLI for metadata inspection. metadata: author: truongduy2611 version: "1.0" --- # App Store Preflight Skill Run pre-submission checks on your iOS/macOS project to catch common App Store rejection patterns. ## Prerequisites - **asc CLI** — Install via Homebrew: `brew install asc` ([App-Store-Connect-CLI](https://github.com/rudrankriyam/App-Store-Connect-CLI)) - **ASC CLI Skills** — [app-store-connect-cli-skills](https://github.com/rudrankriyam/app-store-connect-cli-skills) for `asc` usage patterns - **jq** — Optional, but used by some JSON-inspection examples in the rule docs ## Step 1: Identify App Type Determine which guidelines apply by loading the relevant checklist from `references/guidelines/by-app-type/`. Always start with `all_apps.md`, then add the app-type-specific one.