mobile-store-reviewlisted

Audits a mobile app codebase — Expo/React Native (managed or bare) or native iOS/Android, standalone or inside a Turborepo/monorepo — and reports whether it would pass Apple App Review and Google Play review. Use this skill whenever the user: asks if their app will pass, fail, or get rejected by Apple or Google review; is preparing an App Store or Play Store submission; got a rejection email or resolution center message citing a guideline or policy; is filling out the App Privacy questionnaire or Play Data safety form; is auditing permissions, usage descriptions, a privacy manifest, or account-deletion flow; mentions App Review Guidelines, Play Developer Program Policies, TestFlight, `eas submit`, App Store Connect, or Play Console; or is doing a pre-submission or release-readiness check on a mobile app. Also use when the user says things like "will this get rejected?", "audit my app before I ship it", or "review my app for the stores" — even if they don't name a specific guideline.
eagerworks/skills · ★ 3 · Code & Development · score 69

Install: claude install-skill eagerworks/skills

# Mobile Store Review Skill Audits a mobile app's source and config — not the running app, not the store listing — and reports whether Apple App Review and Google Play review would pass it. Most first-submission rejections are compliance plumbing that's visible in code: a missing usage description, no in-app account-deletion path, a target SDK below the current floor, a privacy declaration that doesn't match what's actually linked. This skill finds those before a human reviewer does. ## Discovery — Do This First Locate the app and classify its stack before checking anything else. **1. Find the mobile app(s).** In a monorepo, check `turbo.json` for app-shaped tasks (`build`, `ios`, `android`) and the workspace globs in `pnpm-workspace.yaml` / `package.json#workspaces` / `turbo.json#packages`. Within candidate packages, look for `app.json`, `app.config.js`/`app.config.ts`, an `expo` dependency, or committed `ios/` + `android/` directories. A monorepo can contain more than one mobile app — audit each separately. **2. Classify the workflow** — this determines which file is the *source of truth*: | Signal | Workflow | Source of truth | |---|---|---| | `app.config.*`/`app.json`, no committed `ios/`/`android/` | Expo managed (CNG) | The resolved Expo config | | `app.config.*`/`app.json` **and** committed `ios/`+`android/` | Expo + prebuilt native dirs | The native files — `app.config.ts` may be stale | | `ios/`+`android/`, no `expo` dependency | Bare React Native | The native