CLI and MCP server that take an iOS app all the way to App Store review over the App Store Connect API —…
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: npx skills. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: Agent 技能. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository beydemirfurkan/appstore-release;first catalogued 2026-10-10;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
appstore-release
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
**Ship an iOS app to App Store review by asking your agent.**
Real output, recorded against the demo below.
Then tell your agent: **"Publish my app for review."**
The agent reads your app from App Store Connect and names everything that stands between it and review. It then fixes whatever Apple's API allows and submits only once nothing is in the way.
Try it without an Apple account
The demo runs against a local stand-in for App Store Connect, so nothing leaves your machine.
How it works
**preflight** reads the app itself — Info.plist, privacy manifest, code — offline, and names what App Review rejects before you build: a permission prompt with no reason, accounts that cannot be deleted, a paywall with no restore. Each finding has the guideline, the file and line, and the fix.
**check** reads the whole app and returns a verdict with an ordered plan. Each finding says whether the tool can fix it or only you can.
**release** writes the listing: build, metadata in every locale, price, age rating, accessibility labels, screenshots, subscriptions with their offers and offer codes, and in-app purchases. It is idempotent; a second run sends nothing.
**submit** sends the version with any new plans and purchases, and refuses unless check says ready. check --wait then follows the review to its outcome.
Apple keeps the App Privacy label in its web UI; check tells you exactly where to click. An app's first subscription or in-app purchase goes with the version by API — and if App Store Connect will not take it, nothing is submitted and you get the clicks instead.
Using Expo? Your store.config.json, eas.json and app.json are read as they are.
Skills
appstore-release reads the plan and hands each finding to the skill that knows that area:
- **app-store-preflight**: what App Review rejects in the app itself, before you submit
- **app-store-screenshot-upload**: exact sizes, iPhone Duo, iPad
- **app-store-age-rating**: the 2026 questionnaire
- **app-store-subscriptions**: plans, free trials, lifetime purchases
- **app-store-rejection**: read the reviewer's message, fix, resubmit
- **ios-code-signing**: EAS certificates and provisioning profiles
- **app-store-testflight**: groups, testers, What to Test, beta review
- **app-store-customer-reviews**: read customer reviews, draft replies, publish each after your OK
Coming from 3.x, where the skills were named asc-*? Remove the old ones, then add again: