What problem does it solve? Releasing an Expo/React Native Android app involves many error-prone steps—version bumping across multiple files, signed AAB builds, Play Console uploads, release notes in seven locales, and store listing updates—where a single missed step (like forgetting to push the branch or bump versionCode) causes failed uploads or inconsistent releases. ## Core Features & Use Cases - Full release pipeline: Sync main, verify baselines (tsc/vitest/lint), test on a physical device via debug builds, determine the next versionCode by querying Play, bump versions in package.json/app.config.ts/CHANGELOG, build a signed AAB, and validate it. - Play upload with safety gates: Upload via scripts/release.mjs with a mandatory dry-run → --validate → --commit sequence, defaulting to the alpha track. - Release notes & store listing: Generate 7-locale release notes under the 500-character Play limit and push listing copy/screenshots via scripts/push-play-listing.mjs. - Use Case: Say "リリースして" (release it) and the Skill walks through device verification, AAB build, tagging with the AAB SHA-1, Play upload, and cleanup—while avoiding documented pitfalls like McAfee occupying port 8081 or pushing only the tag without the branch. ## Quick Start Ask the AI to release a new version of UnitCalc to Google Play, for example: "Bump the version and ship the release to the Play alpha track."