app-store-review

Audit iOS App Store submission readiness for metadata, privacy, IAP, and ATT compliance.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/harshav167/build-ios-apps --skill app-store-review-harshav167
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-store-review
Source: https://github.com/harshav167/build-ios-apps/tree/main/skills/app-store-review
Command: npx skills add https://github.com/harshav167/build-ios-apps --skill app-store-review-harshav167

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

App Store submission readiness is complex and risk-prone; this Skill helps teams pre-emptively identify and fix issues that commonly cause rejections, ensuring metadata accuracy, privacy manifest compliance, and proper IAP/ATT handling before submission.

Core Features & Use Cases

  • Guidance on blocking issues and policy alignment across App Store guidelines (privacy, IAP, ATT, DMA)
  • Pre-submission checklists and reference materials to streamline reviewer experience
  • Use Case: run a universal audit for a new app build and flag potential rejection risks with remediation steps

Quick Start

Audit your current build for App Store submission readiness.

Frequently Asked Questions about app-store-review

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

FAQPage Schema
How do I check my iOS app for App Store submission readiness before uploading?

An App Store submission readiness audit evaluates metadata accuracy, privacy manifests, IAP and StoreKit usage, and ATT state across iPhone and iPad. It flags potential rejection risks with remediation steps to ensure full compliance before you upload your build.

What is a privacy manifest and when do I need it for my iOS app?

A privacy manifest is a required declaration for iOS apps detailing data collection and tracking practices. You need it for App Store submission readiness if your app has tracking considerations or privacy disclosures, ensuring your build satisfies App Store privacy guidelines.

How do I audit IAP and StoreKit usage to prevent App Store rejection?

Auditing IAP and StoreKit usage involves verifying your in-app purchase implementation aligns with App Store guidelines. A submission readiness audit checks your IAP configuration and subscription handling to identify policy misalignment and blocking issues before submission.

Does this App Store review checklist work for apps with subscriptions and ATT tracking?

Yes, this submission readiness audit specifically applies to iOS apps in development with subscriptions, tracking considerations, and privacy disclosures. It evaluates ATT state and IAP usage across iPhone and iPad to ensure compliance before upload.

Why does my app get rejected during App Store review and how can I prevent it?

App Store rejections commonly occur due to metadata inaccuracies, missing privacy manifests, or improper IAP and ATT handling. A pre-submission readiness audit identifies these blocking issues and policy misalignments, providing remediation steps to fix them before upload.

What are the App Store metadata and screenshot guidelines for submission readiness?

App Store metadata and screenshot guidelines require accurate descriptions, proper privacy disclosures, and compliant visual assets. A readiness audit verifies your metadata accuracy and screenshot guidelines to satisfy pre-submission checks and reviewer experience requirements.