Skip to content

skillMobile

Mobile App Release

Prepares an iOS or Android store release: version and build bump, signing check, changelog, screenshots list and review notes, without uploading anything.

npx workspacetemplates add mobile-app-release --tool claude-code

Writes 1 file to .claude/skills/mobile-app-release/

.claude/skills/mobile-app-release/SKILL.md23 lines · 1.9 KBFile
---
name: mobile-app-release
description: "Prepares an iOS or Android store release: version and build bump, signing check, changelog, screenshots list and review notes, without uploading anything."
---

# Mobile app release

Prepare, verify and report. Never upload, submit or change store settings.

## Steps

1. Detect the project: Xcode project or workspace, Gradle app module, Flutter, React Native or Expo. Find the last release tag with `git describe --tags --abbrev=0` and list commits since it.
2. Versions. Show the current marketing version and build number (`CFBundleShortVersionString` and `CFBundleVersion`, or `versionName` and `versionCode`). Propose the next values: build numbers only go up and must never repeat. Apply them only after the user agrees.
3. Configuration audit. Confirm release builds have debugging off, no staging API URLs, no test keys, analytics set to production, and minification enabled on Android. Search shipped code for unfinished-work markers, `localhost` and `10.0.2.2`.
4. Signing. Verify that the signing config exists and names a keystore or profile by reference. Check the provisioning profile and certificate expiry dates where visible. Never print or copy secrets.
5. Permissions and privacy. List every requested permission, check each has a usage description on iOS or a stated reason on Android, and flag any that no code uses.
6. Build a release artifact locally (`xcodebuild archive`, `./gradlew bundleRelease` or the framework equivalent) and report success or the first error.
7. Draft materials: release notes from the commit list, in user language and under 500 characters, plus a list of screenshots that need refreshing because their screens changed.
8. Reviewer notes: demo account steps, anything that needs hardware or a region, and the reason for sensitive permissions.

## Report

A checklist with pass, fail or unknown for each step, then the draft notes. Mark anything you could not verify.

What it does

Store rejections and last-minute surprises usually come from small things nobody checked: a build number reused, a debug flag left on, a permission with no usage string. This skill walks the agent through a release checklist against the actual project files.

It prepares everything and stops before any upload or submission. You get a ready list of what changed, what is missing and what to paste into the store forms.

Example

you › Get the Android app ready for version 2.8.0 on the Play internal track.

agent › versionName 2.7.3 to 2.8.0, versionCode 143 to 144 (applied). Fail: BASE_URL still points at staging in release flavor, src/release/config.kt:6. Warning: READ_CONTACTS is requested but never used. Release bundle builds. Draft notes (212 chars) and 3 screens to re-shoot: onboarding, settings, checkout. Not verified: signing key expiry, kept in the Play console.

Questions

Does it upload the build for me?
No. Uploads and submissions stay with you. The skill stops once the artifact builds and the checklist and notes are ready.
What about my signing keys?
It checks that signing is configured and when a certificate expires, but it never reads key passwords or writes secrets into files or into its report.
  • Flutter State Management

    Skillflutter

    Free
  • Kotlin Android Compose

    Skillkotlin

    Free
  • Offline First Sync

    SkillMobile

    Free
  • React Native Performance

    Skillreact-native

    Free