Skip to content

alirezarezvani/claude-skills / engineering/skills/mobile-release

mobile-release

Verified

Use when shipping an iOS or Android app update to the App Store or Google Play - Apple or Google rejected or warned about a build (ITMS-91053 privacy manifest, required reason API, missing usage description, target API level, 16 KB page size, exported activity, SMS or call log permission, Data safety), a readiness check before submitting an iOS, Android, Flutter or React Native release, or whether to pause, halt or widen a phased or staged rollout from crash rate, ANR rate or Play's bad behavior thresholds. Checks the project with stdlib scripts.

assets/release_checklist.md

View on GitHub
# Mobile release sign-off

Release: ________  Platform: iOS / Android  Owner: ________  Date: ________

## Before upload
- [ ] `ios_privacy_manifest_check.py` exit 0 or 2, every WARN read (iOS)
- [ ] Each declared reason code matches what the code does (named reviewer: ________)
- [ ] Vendored SDKs on versions that ship their own PrivacyInfo.xcprivacy
- [ ] App Store privacy label matches NSPrivacyCollectedDataTypes
- [ ] `android_release_check.py` exit 0 or 2 for the date of submission (Android)
- [ ] Play Console declarations filed for every DECLARATION_REQUIRED permission
- [ ] Data safety form updated for new permissions or SDKs
- [ ] Native libraries 16 KB aligned (`zipalign -c -P 16 -v 4 app.apk`)

## Rollout
- [ ] Baseline release and its crash/ANR counts recorded
- [ ] Gate run at each step; result pasted below
- [ ] Halt owner on call for the first 48 hours: ________

| Step | Date | Users | Crash % | ANR % | Gate | Decision by |
|---|---|---|---|---|---|---|
| | | | | | | |
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall