- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-release-flow -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/rorkai/app-store-connect-cli-skills/tree/HEAD/skills/asc-release-flow来自发布者
Use this skill to carry a release from an approved plan to App Store review.
This skill owns:
Use the preparation section for Game Center item preparation or attachment blockers. Use that reference's assembly and submission sections only after the app version is staged and the multi-item lane is selected. Switch to asc-submission-health for other validation blockers, a stuck submission, cancellation, or retry decisions.
Switch skills within the current task, preserving resolved targets, authorization, and verified progress. A failing gate blocks dependent mutations, not diagnosis or independent authorized work. Continue authorized repairs and resume this flow; request new authority only when repairs exceed the agreed scope.
APP_ID, the version string, VERSION_ID when needed, and BUILD_ID when a build already exists.asc auth login or ASC_* environment variables.IOS unless the app targets another platform../metadata when the workflow applies metadata.--confirm for submission.Do not mix lanes after one has already created a review submission. Inspect the existing submission first and continue through the matching lower-level commands.
Apply this gate to a version that already has the intended build attached. For the staging lane, first complete Stage an existing build; asc release stage attaches the build and runs validation, after which this gate can be evaluated. Do not route an expected pre-staging "build not attached" result to asc-submission-health.
Validate before any submission:
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table
Use strict mode when warnings must stop automation:
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --strict --output table
Digital goods are a hard gate. If the release includes IAPs or subscriptions, stop and run the relevant product checks in asc-submission-health. Resume this flow only after those checks have no blocking issues and the intended product versions are prepared.
For Game Center items, complete only Prepare every item, then return to this flow. Do not assemble or submit the multi-item review submission during readiness.
If app validation reports a Game Center item blocker, stop and use that preparation section. If the only blocker is an unattached build in the staging lane, continue to the staging section. For every other blocker, pause dependent release actions and use asc-submission-health; resume after authorized repairs pass validation.
Use asc release stage to verify the selected build belongs to the app before changing the version, apply or copy metadata, attach the build, and run validation without creating a review submission.
Preview metadata-driven staging:
asc release stage \
--app "APP_ID" \
--version "1.2.3" \
--build-id "BUILD_ID" \
--metadata-dir "./metadata" \
--dry-run \
--output table
Apply the reviewed plan:
asc release stage \
--app "APP_ID" \
--version "1.2.3" \
--build-id "BUILD_ID" \
--metadata-dir "./metadata" \
--confirm
--metadata-dir takes the canonical metadata root that contains app-info/ and version/<version>/, the same layout as asc metadata push --dir. Use --copy-metadata-from "1.2.2" instead of --metadata-dir when carrying localization metadata forward. Add --strict-validate when warnings should fail the stage.
If the metadata plan contains deletes, the dry run and confirmed run both require --allow-deletes. Review those deletes first; the flag also disables fallback to an existing locale when that locale is absent locally.
Use --routing-coverage-file "./coverage.geojson" when the release includes routing app coverage. This experimental step validates the GeoJSON before mutation and stages it before readiness checks.
Structured output includes a validate_build step at the start of steps[]. Match steps by name rather than array position.
Use asc review submit after metadata, review details, availability, build processing, and product readiness are already resolved.
asc review submit --app "APP_ID" --version "1.2.3" --build-id "BUILD_ID" --dry-run --output table
asc review submit --app "APP_ID" --version "1.2.3" --build-id "BUILD_ID" --confirm
Use --version-id "VERSION_ID" instead of --version when the exact version ID is known. Select the build with --build-id, or with --build-number "45" to skip the build-ID lookup; it matches only builds of that app, version string, and platform. Right after an upload, prefer --build-number over --latest, which can still pick the previous upload. Add --wait to wait for processing before attaching.
Use asc publish appstore when the release starts from an IPA or a local Xcode project/workspace.
Preview an IPA upload and submission:
asc publish appstore \
--app "APP_ID" \
--ipa "./App.ipa" \
--version "1.2.3" \
--submit \
--dry-run \
--output table
Run it after reviewing the plan:
asc publish appstore \
--app "APP_ID" \
--ipa "./App.ipa" \
--version "1.2.3" \
--submit \
--wait \
--confirm
For local-build mode, provide --workspace or --project with --scheme instead of --ipa. Use --metadata-dir when the publish command should apply canonical version metadata after ensuring the version.
Omit --submit when the user wants upload and attachment only.
Read references/multi-item-submissions.md when the app version must ship with versioned IAP, subscription, subscription-group, or Game Center items. Add only items the user has resolved and inspected.
Report:
Use asc-submission-health for monitoring, cancellation, rejection diagnosis, or retry decisions.
submit-preflight, submit-create, or release-run shortcuts.--confirm until the dry-run plan matches the requested release.Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release.
---name: asc-release-flowdescription: Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact…---# skills/asc-release-flow/SKILL.md概览
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.
常见问题
从发布者处下载 skills/asc-release-flow/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/rorkai/app-store-connect-cli-skills。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。