submission-preview

Analyze Xcode and macOS source files against Apple's App Review Guidelines.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill submission-preview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submission-preview
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/apple-dev/skills/submission-preview
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill submission-preview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill scans an Xcode/macOS project to detect code-level issues that commonly trigger App Store rejections, saving developers time and reducing last-minute submission failures.

Core Features & Use Cases

  • Project characteristic detection: Automatically determines if the app has accounts, IAP, UGC, background modes, location, HealthKit, third-party login, or tracking to scope relevant checks.
  • Code and plist verification: Searches Info.plist, imports, and source files to validate permission strings, deprecated APIs, background mode implementations, StoreKit usage, and sign-in flows with file:line evidence.
  • Actionable report: Produces a categorized pre-submission report (High/Medium/Passed), a manual verification checklist, and remediation steps tied to specific guideline sections (1–5).
  • Use Case: Run before uploading a build to App Store Connect or when asked "will this pass review" to catch privacy, permission, IAP, and background implementation issues.

Quick Start

Run a submission preview by asking the assistant to run submission-preview on the project and review App Store readiness.

Frequently Asked Questions about submission-preview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Xcode project for App Store rejection reasons before submitting?

A static pre-submission analysis scans your Xcode project's source files and Info.plist to identify common App Store rejection reasons. It validates privacy purpose strings, background modes, and StoreKit implementations against Apple's App Review Guidelines.

What is static analysis for iOS app review compliance?

Static analysis for iOS app review compliance is a preflight code scanning process that detects configuration issues causing App Store rejections. It identifies missing privacy purpose strings, invalid background modes, and incomplete IAP flows.

Does App Store preflight checking work with macOS and iOS Xcode projects?

Yes, App Store preflight checking applies to macOS and iOS Xcode projects. It automatically detects project characteristics like accounts, IAP, background modes, location, and HealthKit to scope relevant guideline checks.

How do I validate Info.plist privacy purpose strings for App Store submission?

To validate Info.plist privacy purpose strings, run a static analysis scan on your Xcode project. It searches Info.plist configurations and source file imports to verify compliance with Apple's privacy requirements.

What are the limitations of static analysis for App Store review guidelines?

Static analysis for App Store guidelines focuses on code-level checks and cannot simulate runtime behavior or human review. It identifies configuration issues, missing permission strings, and deprecated APIs with file:line evidence.

Can I get a remediation checklist for iOS app review guideline violations?

Yes, you can generate a remediation checklist for iOS app review violations. The analysis outputs a categorized pre-submission report with High, Medium, and Passed checks, plus manual verification steps tied to specific guideline sections.