
mobile-release
Pre-submission checks and staged-rollout gating for iOS and Android app store releases.
- version
- 2.14.14
- GitHub stars
- 30.3K
What it does
- Adds
/cs-mobile-releasefor pre-submission checks and/cs-rollout-gatefor PROCEED, HOLD, or HALT rollout decisions - Covers the iOS privacy manifest, required-reason API use, usage-description strings, and vendored SDK manifests
- Enforces Play's target API level by date and form factor, plus 16 KB page alignment read from ELF headers
- Designed for mobile teams shipping updates to the App Store or Google Play that need to stop crash spikes
Get iOS and Android releases through App Store and Google Play review and roll them out safely. Three deterministic stdlib scripts: an iOS check that matches required-reason API use in source against PrivacyInfo.xcprivacy (valid and SDK-only reason codes per category), purpose strings in Info.plist or INFOPLIST_KEY_ settings and vendored SDK manifests; an Android check for Play's dated target API level by form factor, android:exported, debuggable builds, permissions that need a Play Console declaration and 16 KB page alignment read from ELF headers; and a rollout gate that returns PROCEED, HOLD or HALT from crash and ANR counts against the previous release and Play's bad-behavior thresholds. Ships cs-mobile-release agent, /cs-mobile-release and /cs-rollout-gate commands and 3 cited references.
Add marketplace
/plugin marketplace add alirezarezvani/claude-skillsRun it inside Claude Code once, then install the plugin below.
Install
/plugin install mobile-release@claude-code-skillsRun it inside Claude Code after adding the marketplace.
Files
Discovered from sourceMobile Release
Portability: 3 stdlib Python scripts. They read project files only. No network, no store API calls. Rules verified 2026-11-17. Store rules move every year; each script prints the date its table was checked.
Most store rejections and bad rollouts come from a short list of mechanical
misses: an API Apple requires a reason for, a purpose string that was never
added, a targetSdk one level behind, a receiver without android:exported,
a crash spike that was widened to 50% because nobody compared it with the last
release. This skill checks each one before it costs a review cycle.
Workflow
# 1 - iOS: required-reason APIs vs PrivacyInfo.xcprivacy, purpose strings, SDK manifests
python scripts/ios_privacy_manifest_check.py --project ios/
# 2 - Android: Play target API level, exported components, declaration permissions, 16 KB pages
python scripts/android_release_check.py --project android/ --form-factor phone
# 3 - During rollout: compare the new release with the last one, then widen, hold or halt
python scripts/rollout_gate.py --input rollout.csv
Step 1 finds code that uses a required-reason API category (file
timestamps, system boot time, disk space, active keyboards, UserDefaults) and
checks the app manifest declares it with a reason Apple lists for that
category. It blocks invalid and SDK-only reasons, a framework used without its
NS...UsageDescription (Info.plist or INFOPLIST_KEY_ build setting), and
warns when a vendored SDK ships no manifest of its own. Pick the reason that
is true; an upload that passes is not proof the reason is right.
Step 2 reads targetSdk from Gradle (including Capacitor variables.gradle
and version catalogs) and applies Play's dated rule for the form factor. It
blocks debuggable builds and intent-filter components with no
android:exported, and lists permissions that need a Play Console declaration
before release (background location, SMS, all-files access, exact alarms,
foreground service types).
Step 3 needs counts, not percentages: users and crashed users for the baseline and the new release. It halts on Play's bad-behavior thresholds or a statistically significant regression, and holds when the regression is not yet significant or the release has too few users.
Hard rules
- Pick the reason code the stated use supports. When the user says how the API is used, name the one matching code (for example C617.1 for timestamps of files in the app container); ask only when the use is unknown.
- A BLOCKER means do not submit. Fix it, re-run, then upload.
- Never declare a reason code to make the check pass. Ask what the code does with the API, then pick the reason.
- The app's manifest cannot cover an SDK. Update the SDK to a version that ships its own manifest.
- Never widen a rollout on a percentage alone. Feed the gate counts for both releases.
- iOS cannot roll back. A paused phased release is still downloadable by hand; plan the fix or pull the build.
- Re-check dates. If today is past a date in a script's rule table, confirm against the official page in the references.
Scripts
| Script | Role | Exit codes |
|---|---|---|
scripts/ios_privacy_manifest_check.py | Required-reason APIs, reason codes, purpose strings, SDK manifests, tracking keys | 0 · 2 warnings · 3 bad input · 4 blocked |
scripts/android_release_check.py | Target API level by date and form factor, exported, debuggable, declarations, 16 KB | 0 · 2 warnings · 3 bad input · 4 blocked |
scripts/rollout_gate.py | PROCEED / HOLD / HALT from crash and ANR counts vs baseline | 0 proceed · 2 hold · 3 bad input · 4 halt |
All support --help, --sample and --output json.
References and assets
references/ios_submission_rules.md: privacy manifests, reason codes, purpose strings, SDK and Xcode minimums (7 sources)references/play_release_rules.md: target API levels, exported, declarations, Data safety, 16 KB pages (7 sources)references/staged_rollout_gates.md: phased vs staged rollout, vitals thresholds, the regression test (6 sources)assets/rollout.example.csv: input format for the gateassets/release_checklist.md: submission and rollout sign-off
Readme
mobile-release
Get an iOS or Android release through store review and roll it out without widening a crash spike. Three stdlib Python scripts; no network, no store API.
| Script | What it stops |
|---|---|
ios_privacy_manifest_check.py | Uploads refused for an undeclared required-reason API (ITMS-91053), invalid or SDK-only reason codes, a missing NS...UsageDescription, SDKs without their own manifest |
android_release_check.py | targetSdk below Play's level for the date and form factor, intent-filter components without android:exported, debuggable builds, permissions needing a Play declaration, prebuilt .so files not 16 KB aligned |
rollout_gate.py | Widening a staged or phased rollout while crash or ANR rates are above Play's thresholds or significantly worse than the last release |
/plugin install mobile-release@claude-code-skills
/cs-mobile-release ./app # pre-submission check
/cs-rollout-gate rollout.csv # PROCEED / HOLD / HALT
Rules were verified on 2026-11-17 against Apple and Android developer
documentation; each script prints that date. Store rules change yearly, so
re-check the official pages listed in skills/mobile-release/references/
after any date in the rule tables.
Agent: cs-mobile-release. License: MIT.
Details
- Marketplace
- alirezarezvani/claude-skills
- Source
- engineering/mobile-release
- Author
- Alireza Rezvani
- Category
- Development
- Keywords
- mobile, ios, android, app-store, google-play, privacy-manifest, target-api-level, staged-rollout, release, crash-rate
More from alirezarezvani/claude-skills
All 130- monetizev2.14.11
- month-end-closev2.14.5
- nis2-readinessv2.14.13
- notebooklmv2.14.5
- patentv2.14.5
- pm-skillsv2.14.6
- power-user-coachv2.14.5
- product-managerv2.2.0
- product-skillsv2.14.11
- prompt-governancev2.14.5
- pulsev2.14.5
- pwv2.14.6
- ra-qm-skillsv2.14.14
- readme-polishv2.14.12
- reflect-skillv2.14.5
- research-ops-skillsv2.14.6
- research-orchestratorv2.14.7
- research-summarizerv2.14.5
- roastv2.14.6
- scrum-masterv2.2.0
- security-guidancev2.14.5
- self-improving-agentv2.14.11
- skill-doctorv2.14.1
- skill-retrov2.14.6
Similar to mobile-release
More Mobile Development
ui-ux-pro-maxnextlevelbuilder/ui-ux-pro-max-skill152.6K starsProfessional UI/UX design intelligence for AI coding assistants. Includes searchable databases of styles, colors, typography, charts, and UX guidelines for Reac
agentic-bundle-aas-mobile-app-buildersickn33/agentic-awesome-skills50.1K starsInstall the "AAS Mobile App Builder" editorial skill bundle for Claude Code.
apollo-skillsanthropics/claude-plugins-official47.9K starsApollo GraphQL agent skills for Claude Code — Apollo Client, Server, Federation, Connectors, Router, Rover CLI, iOS, Kotlin, and the Apollo MCP server. Covers s
frontend-mobile-developmentwshobson/agents42.8K starsFrontend UI development and mobile application implementation across platforms
voltagent-core-devVoltAgent/awesome-claude-code-subagents26.6K starsEssential development subagents for everyday coding tasks - backend, frontend, fullstack, mobile, and API design
e2etester-army/e2e14K starsWrite, run, and debug end-to-end tests for web and mobile apps with e2e.