AgentSkillsCN

native-app-publish-ready

为移动应用提供全面的应用商店提交就绪性检查工具。在审核iOS App Store与Google Play Store的要求时,包括构建配置、隐私合规、商店素材、元数据、技术要求,以及常见的拒绝原因。当用户提出“检查我的应用是否已准备好提交”“为应用商店做审查”“应用商店检查清单”“提交前检查”“已准备好上架Play Store”“已准备好上架App Store”“提交就绪性”等需求时使用此功能。支持原生iOS(Swift/ObjC)、原生Android(Kotlin/Java)、Flutter以及React Native(包括Expo)项目。

SKILL.md
--- frontmatter
name: native-app-publish-ready
description: Comprehensive app store submission readiness checker for mobile apps. Audits iOS App Store and Google Play Store requirements including build config, privacy compliance, store assets, metadata, technical requirements, and common rejection causes. Use when the user asks to "check if my app is ready to submit", "review for app store", "app store checklist", "pre-submission check", "ready for Play Store", "ready for App Store", "submission readiness", or wants to audit a mobile app before publishing. Supports native iOS (Swift/ObjC), native Android (Kotlin/Java), Flutter, and React Native (including Expo) projects.

App Store Readiness

Audit a mobile app project for app store submission readiness. Detect the project type automatically and check against platform-specific requirements for the Apple App Store and Google Play Store.

Workflow

  1. Detect project type and target platforms
  2. Run the automated scanner
  3. Load relevant platform checklist(s) and review results
  4. Walk through items that cannot be automated
  5. Produce a final readiness report

Step 1: Detect and Scan

Run the scanner to auto-detect framework and platforms and perform automated checks:

bash
python3 <skill-path>/scripts/check_project.py <project-root>

Output: JSON with project_type (framework + platforms), summary (error/warning/pass counts), and issues array.

Step 2: Load Platform Checklists

Based on detected project type, read the relevant reference files for the full checklist:

DetectedRead
iOS targetreferences/ios.md
Android targetreferences/android.md
Flutter frameworkAlso references/flutter.md
React Native frameworkAlso references/react-native.md

Each reference file contains a complete checklist organized by category. Use these to supplement the automated scan with manual review items.

Step 3: Review Automated Results

Present scanner results grouped by severity:

  1. Errors (blockers) - Must fix before submission
  2. Warnings (risks) - Likely to cause rejection or should be addressed
  3. Passed - Checks that look good

Step 4: Manual Review

Walk through critical items that cannot be verified by scanning files alone:

Store Assets and Metadata

  • Screenshots for all required device sizes
  • App description, keywords, promotional text within character limits
  • Privacy policy URL live and accessible
  • Support URL or email functional
  • Age rating questionnaire accuracy

Testing

  • Tested on physical devices
  • Tested on oldest and newest supported OS versions
  • In-app purchases tested in sandbox (if applicable)
  • Push notifications verified end-to-end
  • Deep links and universal links working

Legal and Compliance

  • Privacy policy hosted and URL submitted
  • Data collection declarations match actual behavior
  • ATT prompt before tracking (iOS)
  • Account deletion offered (required by both stores)
  • COPPA compliance if targeting children

App Review Preparation

  • Demo account credentials ready (if login required)
  • Review notes for non-obvious features
  • Contact information current

Step 5: Produce Report

Summarize findings using this structure:

code
# App Store Readiness Report

**Project:** [name]
**Framework:** [detected] | **Platforms:** [ios/android]
**Date:** [date]

## Blockers (must fix before submission)
- ...

## Warnings (address before submission)
- ...

## Manual Checklist
- [ ] [items requiring human verification]

## Passed
- ...

## Recommendation
[Ready to submit / Not ready, N blockers remain]