review-readiness-check

Detects App Store review-blocking configuration issues in iOS and macOS projects before submission.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/tvh25082004/Badminton --skill review-readiness-check-tvh25082004
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-readiness-check
Source: https://github.com/tvh25082004/Badminton/tree/main/.claude/skills/apple-app-review/quality/review-readiness-check
Command: npx skills add https://github.com/tvh25082004/Badminton --skill review-readiness-check-tvh25082004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Apps are frequently rejected by Apple App Review for preventable configuration mistakes such as sub-1.0 version numbers, beta labels in the app name, staging endpoints, missing demo credentials, and forced-update gates that lock reviewers out of the submitted binary. ## Core Features & Use Cases - Configuration Scanning: Checks MARKETING_VERSION in project.pbxproj, CFBundleDisplayName in Info.plist, and hardcoded staging or localhost URLs in Swift source files. - Reviewer Access Validation: Verifies that demo credentials are documented when the app requires login, and flags forced-update gates that block access to the submitted build. - Prioritized Findings Report: Outputs findings grouped by severity (CRITICAL, HIGH, MEDIUM, LOW) with file paths, line numbers, and mapped App Review Guidelines 2.1 and 2.3. - Use Case: Before submitting an iOS app, run this check to catch a 0.9 marketing version, a staging API base URL, and missing review notes so you can fix them before Apple rejects the build. ## Quick Start Ask the assistant to run a review readiness check on your iOS project root before submitting to the App Store.

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 if my iOS app is ready for App Store review?▼

Run a review readiness check that scans your Xcode project for common rejection triggers: sub-1.0 MARKETING_VERSION values, beta or test wording in CFBundleDisplayName, staging URLs in Swift code, and missing demo credentials for login-required apps.

Why was my app rejected under App Review Guideline 2.1?▼

Guideline 2.1 rejections commonly occur when reviewers cannot access the app, such as missing demo login credentials, SMS OTP tied to the developer's phone, or a forced-update gate blocking the submitted binary. Sub-1.0 version numbers also signal an incomplete app.

Does this check work with React Native or Flutter projects?▼

Yes. The check works on Swift, Objective-C, React Native, and Flutter projects because it relies on Glob, Grep, and Read operations against project files, Info.plist, and source code rather than platform-specific tooling.

Can I use this check as part of a larger App Store audit?▼

Yes. The skill accepts an optional shared_context input from an orchestrating appstore-full-audit Phase 1, which skips its own context collection phase and reuses pre-collected project file locations.

Does the review readiness check modify my project files?▼

No. The check is strictly read-only and makes no network calls. It only reads project files and reports findings with file paths and line numbers; all fixes must be applied manually by the developer.