asc-release-flow
Release flow (readiness-first)
Use this skill when the question is "Can my app be submitted now?" or when the user wants to prepare and submit an App Store version with the current asc command surface.
Preconditions
- Resolve
APP_ID, version string,VERSION_IDwhen needed, andBUILD_IDup front. - Ensure auth is configured with
asc auth loginorASC_*environment variables. - Have canonical metadata in
./metadatawhen using metadata-driven staging. - Treat
asc web ...commands as optional experimental escape hatches for flows not covered by the public API.
Answer order
- Say whether the app is ready right now.
- Name the blocking issues.
- Separate public-API fixes from web-session or manual fixes.
- Give the next exact command to run.
Blockers usually fall into:
More from rudrankriyam/asc-skills
asc-cli-usage
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
762asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
714asc-id-resolver
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
695asc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
688asc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
679asc-xcode-build
Build, archive, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.
675