Skip to content
Back to search

appstore-review-skill

SkillGitHubIncomplete

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/devsemih--appstore-review-skill/badge.svg)](/listings/devsemih--appstore-review-skill)

HTML

<a href="/listings/devsemih--appstore-review-skill"><img src="/api/listings/devsemih--appstore-review-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

With the plugin manager (recommended):

/plugin marketplace add devsemih/appstore-review-skill
/plugin install appstore-review-skill

Or clone it into your skills folder:

git clone https://github.com/devsemih/appstore-review-skill ~/.claude/skills/appstore-review-skill

Restart Claude Code after installing. To update, run `/plugin marketplace update`, or `git pull` inside the clone.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 42 lines
  1. {
  2. "$schema": "https://raw.githubusercontent.com/anthropics/claude-code/refs/heads/main/marketplace/marketplace.schema.json",
  3. "name": "appstore-review-skill",
  4. "owner": {
  5. "name": "Semih Aslan"
  6. },
  7. "metadata": {
  8. "description": "App Store and Google Play review policy compliance checker for mobile apps"
  9. },
  10. "plugins": [
  11. {
  12. "name": "appstore-review-skill",
  13. "source": "./",
  14. "description": "App Store & Google Play rejection checker for mobile apps: audits your project (and built .ipa/.aab) against Apple's App Review Guidelines and Google Play policies before you submit, applies safe fixes, and turns rejection messages into root-cause fixes and Resolution Center replies. Works with Swift, Kotlin, Flutter, React Native, Expo, KMP, .NET MAUI, Capacitor/Cordova/Ionic and Unity.",
  15. "version": "2.0.0",
  16. "author": {
  17. "name": "Semih Aslan"
  18. },
  19. "repository": "https://github.com/devsemih/appstore-review-skill",
  20. "license": "MIT",
  21. "category": "development",
  22. "keywords": [
  23. "ios",
  24. "android",
  25. "app-store",
  26. "google-play",
  27. "review-guidelines",
  28. "play-policy",
  29. "apple",
  30. "swift",
  31. "kotlin",
  32. "flutter",
  33. "react-native",
  34. "expo",
  35. "app-review",
  36. "rejection",
  37. "privacy-manifest",
  38. "claude-code-plugin"
  39. ]
  40. }
  41. ]
  42. }
README.md · README · 198 lines
  1. # appstore-review-skill
  2. A Claude Code plugin that checks iOS and Android apps against Apple's App Review Guidelines and Google Play's Developer Program Policies before you submit. When a review comes back rejected, it finds the cause in your code and drafts the reply.
  3. [![GitHub stars](https://img.shields.io/github/stars/devsemih/appstore-review-skill?style=flat)](https://github.com/devsemih/appstore-review-skill/stargazers)
  4. [![Version](https://img.shields.io/github/v/release/devsemih/appstore-review-skill?label=version)](https://github.com/devsemih/appstore-review-skill/releases)
  5. [![Apple guidelines](https://img.shields.io/badge/Apple%20guidelines-Oct%2016%2C%202026-black)](https://developer.apple.com/app-store/review/guidelines/)
  6. [![Play policies](https://img.shields.io/badge/Play%20policies-Oct%2029%2C%202026-green)](https://play.google/developer-content-policy/)
  7. [![License: MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
  8. ![Demo: App Store audit, fix mode, Google Play audit and a rejection reply](assets/demo.gif)
  9. <sub>The demo uses made-up projects. Run `python3 assets/render-demo.py` to regenerate it.</sub>
  10. ## Commands
  11. | Command | What it does |
  12. |---------|--------------|
  13. | `/appstore-review` | Audits your project, and optionally the built `.ipa`, against the [App Store Review Guidelines](https://developer.apple.com/app-store/review/guidelines/) |
  14. | `/playstore-review` | Audits your project, and optionally the `.aab` or `.apk`, against the [Google Play Developer Program Policies](https://play.google/developer-content-policy/) |
  15. | `/appstore-rejection` | Takes an App Review rejection message, finds the cause in your code, proposes a fix and drafts a Resolution Center reply |
  16. | `/playstore-rejection` | Takes a Google Play policy email, finds the cause, tells you whether to fix or appeal, lists the Play Console forms to update and drafts the appeal |
  17. Supported project types: Swift, Kotlin/Java, Flutter, React Native, Expo, Kotlin Multiplatform, .NET MAUI, Capacitor, Cordova, Ionic and Unity.
  18. ## Installation
  19. With the plugin manager (recommended):
  20. ```
  21. /plugin marketplace add devsemih/appstore-review-skill
  22. /plugin install appstore-review-skill
  23. ```
  24. Or clone it into your skills folder:
  25. ```bash
  26. git clone https://github.com/devsemih/appstore-review-skill ~/.claude/skills/appstore-review-skill
  27. ```
  28. Restart Claude Code after installing. To update, run `/plugin marketplace update`, or `git pull` inside the clone.
  29. ## Usage
  30. Run these inside your project in Claude Code:
  31. ```
  32. /appstore-review # audit the project for the App Store
  33. /appstore-review --build build/MyApp.ipa # also inspect the built binary
  34. /appstore-review --fix # audit, then apply the safe fixes
  35. /playstore-review --build app/build/outputs/bundle/release/app-release.aab
  36. ```
  37. If you were rejected, paste the message or point to a file:
  38. ```
  39. /appstore-rejection Guideline 5.1.1(v) - Data Collection and Storage. We noticed that your app supports account creation but does not include an option to initiate account deletion...
  40. /playstore-rejection path/to/policy-email.txt
  41. ```
  42. You get the rule that was cited, the root cause with a `file:line`, a proposed fix (applied only after you confirm) and a reply you can paste into the Resolution Center or the Play Console appeal form.
  43. ## What's new in 2.0
  44. - Two new commands, `/appstore-rejection` and `/playstore-rejection`.
  45. - `--build` inspects the built app. On iOS it looks for the privacy manifest problems behind ITMS-91053, ITMS-91061 and ITMS-90683 emails. On Android it reads the merged manifest, including permissions added by SDKs.
  46. - `--fix` applies safe, mechanical fixes such as purpose strings, privacy manifest entries, ATS exceptions and unused permissions. Larger changes are planned first and wait for your approval.
  47. - Apple's guidelines are updated to the October 16, 2026 revision and Google Play's policies to the October 29, 2026 update.
  48. - Reports are more reliable. The audit runs as three parallel subagents, every finding has a confidence level and a `file:line`, every critical finding is checked again before it is reported, and items you have to verify in App Store Connect or Play Console are listed separately.
  49. The full list is in the [CHANGELOG](CHANGELOG.md).
  50. ## How it works
  51. 1. Detect the framework, config files, dependencies and features, and write them into one short summary.
  52. 2. Optionally inspect the built `.ipa` or `.aab`, since that is what the store actually reviews.
  53. 3. Run three subagents in parallel. Each one loads only its part of the guidelines: safety and performance, business and design, or privacy and legal.
  54. 4. Re-check every critical finding at its `file:line`, merge duplicates and run a final pass over the ten most common rejection reasons.
  55. 5. Write the report with critical issues, warnings, recommendations, manual checks and a verdict of LOW RISK, NEEDS FIXES or HIGH RISK.
  56. 6. With `--fix`, apply the safe fixes, propose the larger ones, re-check and print a summary of what changed.
  57. The guideline text is included in [`references/`](references/), split by section, so the skill quotes the actual rule instead of recalling it from memory.
  58. ## Accuracy
  59. <!-- EVAL_RESULTS -->
  60. The [`evals/`](evals/) folder contains fixture apps with planted violations, plus decoys that look suspicious but are fine. It runs with `claude plugin eval`; see [`evals/README.md`](evals/README.md) to try it yourself. If you hit a false positive, please [report it](https://github.com/devsemih/appstore-review-skill/issues/new?template=false-positive.yml) so it can become a test case.
  61. ## What gets checked
  62. ### `/appstore-review`
  63. Section 1, Safety
  64. - Objectionable content in strings and resources
  65. - User generated content and AI content creation apps (guideline 1.2, updated October 2026): filtering, reporting, blocking and protection against nonconsensual imagery
  66. - Kids Category rules, medical apps, physical harm
  67. - Support and contact information
  68. - Data security: ATS, hardcoded server secrets, secure storage
  69. Section 2, Performance
  70. - Placeholder content, debug code and staging URLs in release builds
  71. - Beta, trial or demo labels in the production app
  72. - Every `NS*UsageDescription` checked against the SDKs that need it
  73. - Mentions of other platforms in user-facing text (2.3.10)
  74. - Hidden or dormant features (2.5.19, new in October 2026)
  75. - iPad support, private APIs, dynamic code loading, background modes, IPv6
  76. Section 3, Business
  77. - In-app purchase for digital goods, and Stripe or PayPal used for digital content
  78. - External purchase links and entitlements (3.1.1(a))
  79. - Restore purchases, and subscription terms shown before the purchase button
  80. - Loot box odds, review prompts, crypto, loans and trading apps
  81. Section 4, Design
  82. - Minimum functionality: web wrappers and template apps
  83. - Spam (4.3, rewritten in October 2026): white-label setups with many bundle IDs, saturated categories
  84. - Login services (4.8): an equivalent privacy-focused login when social login is offered, with the listed exceptions
  85. - Extensions, App Clips, Live Activities, push notifications, Apple Pay, mini apps
  86. Section 5, Privacy and legal
  87. - `PrivacyInfo.xcprivacy`, required-reason APIs and third-party SDK manifests (with `--build`, based on the actual binary)
  88. - Account deletion when the app lets users create an account
  89. - App Tracking Transparency for ad and analytics SDKs
  90. - Health, kids and location data, intellectual property, gambling, VPN, MDM and dark patterns
  91. ### `/playstore-review`
  92. - Privacy and user data: privacy policy inside the app, Data safety declarations for each SDK, prominent disclosure, account deletion in the app and on the web, Advertising ID
  93. - Permissions: SMS and Call Log (including the January 2027 change to call-based verification), `QUERY_ALL_PACKAGES`, `MANAGE_EXTERNAL_STORAGE`, Accessibility, the new Local Network and Contacts declarations, minimum location scope and the location button, the Photo Picker, foreground service types, exact alarms, full-screen intents and unused permissions
  94. - Monetization and ads: Play Billing for digital goods, subscription and trial disclosures including eligibility-based discounts, disruptive ads, consent before personalized ads
  95. - Restricted content: financial services and loans, gambling, user generated content, health, blockchain, AI-generated content, age-restricted features
  96. - Abuse and deception: dynamic code loading, hidden features, review manipulation, AppFunctions, ad fraud, fake system dialogs
  97. - Families: certified ad SDKs only, no Advertising ID in apps for children, neutral age screens
  98. - Technical: target API level, `debuggable`, cleartext traffic, committed keystores and service account keys, store listing metadata
  99. ## Example report
  100. <details>
  101. <summary>Expo project, App Store (shortened)</summary>
  102. ```
  103. # App Store Review Compliance Report
  104. ## Project Summary
  105. - App Name: Pulse (5 chars) Bundle ID: com.pulsefit.app
  106. - Framework: Expo SDK 57 (managed) Deployment Target: iOS 16.0
  107. - Build inspected: yes (build/Pulse.ipa) Guidelines version: October 16, 2026
  108. ## Critical Issues (Will Likely Cause Rejection)
  109. ### [CRITICAL] Guideline 4.8: Login Services
  110. **Confidence:** High
  111. **Issue:** Google sign-in creates the main account and no equivalent privacy-focused login is offered.
  112. **Evidence:** `app/(auth)/login.tsx:23`, `Google.useAuthRequest({...})`. Searched for expo-apple-authentication and AppleAuthentication, found neither.
  113. **Fix:** Run npx expo install expo-apple-authentication, add the Apple button and set ios.usesAppleSignIn to true.
  114. ### [CRITICAL] Guideline 5.1.1: Privacy manifest (ITMS-91053)
  115. **Confidence:** High
  116. **Issue:** ExpoFileSystem uses disk space APIs, but no privacy manifest declares the DiskSpace category.
  117. **Evidence:** build inspection: `POSSIBLE ITMS-91053: framework 'ExpoFileSystem' references NSPrivacyAccessedAPICategoryDiskSpace APIs ...`
  118. **Fix:** Add the category with reason E174.1 under expo.ios.privacyManifests in app.json.
  119. ## Manual Check Required
  120. - [ ] Demo account for the login in App Review Information
  121. - [ ] Privacy nutrition labels: crash data (Sentry), product interaction (PostHog)
  122. - [ ] Screenshots and creative assets follow 2.3.3 and 2.3.14
  123. ## Final Verdict
  124. **HIGH RISK**: add Sign in with Apple and fix the privacy manifest first.
  125. Run /appstore-review --fix to apply the safe fixes automatically (2 available).
  126. ```
  127. </details>
  128. ## Policy versions
  129. | Commands | Source | Version |
  130. |----------|--------|---------|
  131. | `/appstore-review`, `/appstore-rejection` | [App Store Review Guidelines](https://developer.apple.com/app-store/review/guidelines/), sections 1 to 5, full text split by section | October 16, 2026 |
  132. | `/playstore-review`, `/playstore-rejection` | [Google Play Developer Program Policies](https://play.google/developer-content-policy/), all policy areas, summarized | July 2026 plus the October 29, 2026 update |
  133. Apple and Google change these policies several times a year. If something looks out of date, please open an issue or a pull request.
  134. ## Contributing
  135. Pull requests are welcome. These help the most:
  136. - [Share a rejection](https://github.com/devsemih/appstore-review-skill/issues/new?template=rejection-report.yml). Real rejections turn into new checks and test cases.
  137. - [Report a false positive](https://github.com/devsemih/appstore-review-skill/issues/new?template=false-positive.yml).
  138. - Add a check in `skills/*/checks/*.md` together with a test case in `evals/`.
  139. - Update the policy text in `references/appstore/` or `references/playstore/`.
  140. ## License
  141. MIT, see [LICENSE](LICENSE).
  142. This plugin checks your app against publicly available Apple and Google policies. It can't guarantee approval, so always read the official [App Store guidelines](https://developer.apple.com/app-store/review/guidelines/) and [Google Play policies](https://play.google/developer-content-policy/) before you submit.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.