skills.rest
cruisediary
cruisediaryCOMMUNITY
Explore all skills by this author →
GitHub

review-readiness-check

Detect App Store submission blockers in iOS/macOS Xcode projects.

13|1|Updated Mar 29, 2026
Search Tags:#ios#macos#review#quality-check#app-store#submission#config-validation
One-click install
npx skills add https://github.com/cruisediary/apple-app-review-skills --skill review-readiness-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-readiness-check
Source: https://github.com/cruisediary/apple-app-review-skills/tree/main/skills/quality/review-readiness-check
Command: npx skills add https://github.com/cruisediary/apple-app-review-skills --skill review-readiness-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and surfaces App Store submission blockers in iOS/macOS projects to reduce rejections by catching common issues before submission.

Core Features & Use Cases

  • Sub-1.0 version detection in marketing version and CFBundleShortVersionString.
  • Beta/alpha terms detection in app display name (CFBundleDisplayName) and bundle name.
  • Detection of staging or non-production endpoints in code and configuration.
  • Validation of demo credentials and reviewer notes for login-required apps.
  • Prioritized findings with actionable remediation steps and file paths.

Quick Start

Run the readiness check on your iOS/macOS project to surface submission blockers before App Store review.

Frequently Asked Questions about review-readiness-check

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 blockers before review?▼

App Store submission blockers are identified by scanning Xcode projects to validate marketing versions, display names, production endpoints, and reviewer notes, producing prioritized remediation steps with file paths.

What causes App Store rejection under Guideline 2.1 and 2.3 for iOS apps?▼

App Store rejections under Guidelines 2.1 and 2.3 often stem from sub-1.0 marketing versions, beta terms in CFBundleDisplayName, staging endpoints, or missing demo credentials, which preflight checks surface before submission.

How do I validate production URLs and demo credentials for App Store review?▼

Validate production URLs and demo credentials by running pre-submission checks that detect non-production endpoints in code configuration and verify reviewer notes scenarios for login-required apps.

Can I run preflight checks on macOS projects to detect staging endpoints and naming issues?▼

Preflight checks support macOS projects by detecting beta or alpha terms in bundle names, validating marketing versions, and surfacing staging or non-production endpoints in code and configuration files.

What's the best way to prevent App Store rejections from beta terms in app display names?▼

Prevent App Store rejections from beta terms by detecting beta or alpha labels in CFBundleDisplayName and bundle names during pre-submission readiness checks, which report findings with actionable file paths.

Related Skills

Explore More Software Engineering Skills→
firstloophqfirstloophq
9

version-bump

Increment CFBundleShortVersionString and CFBundleVersion in macOS Info.plist files.

Official
Intermediate
YehudaFrankelYehudaFrankel
16

environment-check

Diagnose environment configurations and generate deployment readiness reports.

Community
Intermediate
hanamizukihanamizuki
127

asc-xcode-build

Automate iOS/macOS app building, archiving, and exporting with asc and xcodebuild.

Community
Intermediate
OMIXECOMIXEC
1

app-store-preflight-skills

Scan Xcode projects for App Store submission risks and generate remediation plans.

Community
Intermediate