mobile-release

Automates mobile version bumps, localized release notes, and App Store and Google Play releases.

275|32|Updated Oct 2, 2020
One-click install
npx skills add https://github.com/bex-co/beancount-io --skill mobile-release-bex-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-release
Source: https://github.com/bex-co/beancount-io/tree/main/.agents/skills/mobile-release
Command: npx skills add https://github.com/bex-co/beancount-io --skill mobile-release-bex-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a mobile app to both the Apple App Store and Google Play involves many error-prone steps: summarizing changes, bumping versions, localizing release notes, staging store listings, triggering builds, and verifying submissions. This Skill carries a release through preparation, verification, shipping, and both stores without losing track of state. ## Core Features & Use Cases - Release State Inspection: Compares the previous mobile tag to the candidate release, checks GitHub release runs, EAS builds, App Store Connect versions, and Google Play tracks before acting. - Localized Store Preparation: Generates release notes across all Play locales, stages Apple listing metadata and screenshots with plan/approve/apply verification, and records a staging receipt. - End-to-End Shipping and Recovery: Pushes to main to trigger the release workflow, follows EAS builds and submissions, resumes failed platform submissions by exact build ID, and reports per-store status. - Use Case: Ask the agent to cut a mobile release; it summarizes changes since the last tag, bumps the version, prepares localized listings, ships the build, and reports when both stores are live. ## Quick Start Use $mobile-release to summarize changes since the last release, bump the mobile version, and release to the Apple App Store and Google Play.

Frequently Asked Questions about mobile-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release a mobile app to both the App Store and Google Play?

Invoke $mobile-release with optional release context. It summarizes changes since the previous mobile tag, bumps the version, prepares localized notes and listings, pushes to trigger the release workflow, and completes each store's submission steps.

How do I prepare release notes without publishing to the stores?

Give an explicit stop signal such as "prepare only" or "do not publish yet". The Skill completes local notes, the version bump, and applicable validation without creating remote store resources, pushing, building, or submitting.

Can a failed Android or iOS submission be resumed without rebuilding?

Yes. The Skill inspects the failure, then resumes the failed platform using its exact EAS build ID. It never uses submit --latest, deletes release tags to retrigger everything, or rebuilds the platform that already succeeded.

Does the release workflow support localized store listings?

Yes. It fills whatsNew metadata for every locale, generates Google Play listings across all 16 Play locales from canonical metadata, and stages Apple listing copy and screenshots with a plan, review, and apply verification flow.

What happens when Google Play credentials are missing?

The Skill inspects the effective Android submission settings and names the exact missing credential or access without exposing secrets. It completes independent authorized iOS work and reports Android as blocked rather than claiming both stores released.

Why does the Skill check the Expo SDK version before an iOS release?

Apps built with the iOS 27 SDK require the scene-based life cycle adopted in expo 58.0.0-preview.0. If the pinned Expo version is earlier, the build fails to launch, so the Skill stops and reports the SDK upgrade as the release blocker.