asc-release-flow
Skill6 starsChanged 33 days agoMITView on GitHub
End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store.
9 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- VelimirMueller/claude-skillstheir own version, first seen Nov 1, 2026
- VelimirMueller/ai-development-skillstheir own version, first seen Nov 1, 2026
- deonmenezes/mobile-app-skilltheir own version, first seen Nov 1, 2026
- rorkai/app-store-connect-cli-skillstheir own version, first seen Oct 26, 2026
- CamilleScholtz/swmpctheir own version, first seen Oct 8, 2026
- malpern/VoxClawtheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- kumaran-is/claude-code-onboarding★ 3572% same
Wrote their own version · 8
- rudrankriyam/app-store-connect-cli-skills★ 1.1ksame name
- rorkai/app-store-connect-cli-skills★ 1.1ksame name
- CamilleScholtz/swmpc★ 239same name
- malpern/VoxClaw★ 208same name
- VelimirMueller/ai-development-skills★ 7same name
- VelimirMueller/claude-skills★ 7same name
- deonmenezes/mobile-app-skill★ 4same name
- moasq/ios-dev-agent★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository79 other files it gives its agents.
- adr-phase-coverageSkill
- aposd-red-flag-reviewSkill
- apple-on-device-aiSkill
- artifact-gatesSkill
- asc-app-create-uiSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-revenuecat-catalog-syncSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- choose-boring-technologySkill
- ci-preflightSkill
- conways-lawSkill
- cost-routingSkill
- cost-tier-routingSkill
- cunninghams-lawSkill
- ddd-strategic-auditSkill
- ddd-tactical-reviewSkill
- debug-test-captureSkill
- developing-ios-appsSkill
- doerrs-lawSkill
- fitts-lawSkill
- fix-regression-guardSkill
- galls-lawSkill
- goodharts-lawSkill
- greenspuns-tenth-ruleSkill
- gsd-core-hooksSkill
- hofstadters-lawSkill
- hyrums-lawSkill
- ios-accessibilitySkill
- ios-simulator-boot-healthSkill
- kerckhoffs-principleSkill
- kernighans-lawSkill
- knuths-optimization-principleSkill
- lady-lovelaces-objectionSkill
- leaky-abstractionsSkill
- linuss-lawSkill
- mobile-ios-designSkill
- money-boundary-judgmentSkill
- moores-lawSkill
- no-deferSkill
- norvigs-lawSkill
- parkinsons-lawSkill
- peter-principleSkill
- postels-lawSkill
- post-fix-traceSkill
- qa-test-architectSkill
- rubber-duckSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when you need to get a new build into TestFlight or submit to the App Store.
- Very specific: line 11
Ensure credentials are set (asc auth login or ASC_* env vars).
- Distinctive: line 12
Use a new build number for each upload.
- Very specific: line 13
Prefer ASC_APP_ID or pass --app explicitly.
- Distinctive: line 36
Check or cancel submission:
- Distinctive: line 92
When releasing the same version across platforms:
- Distinctive: line 94
Create version for each platform if not exists
- Very specific: line 110
Always use --help to verify flags for the exact command.
- Very specific: line 111
Use --output table / --output markdown for human-readable output.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release flow (TestFlight and App Store)
Use this skill when you need to get a new build into TestFlight or submit to the App Store.
Preconditions
- Ensure credentials are set (
asc auth loginorASC_*env vars). - Use a new build number for each upload.
- Prefer
ASC_APP_IDor pass--appexplicitly. - Build must have encryption compliance resolved (see asc-submission-health skill).
iOS Release
Preferred end-to-end commands
- TestFlight:
asc publish testflight --app <APP_ID> --ipa <PATH> --group <GROUP_ID>[,<GROUP_ID>]- Optional:
--wait,--notify,--platform,--poll-interval,--timeout
- App Store:
asc publish appstore --app <APP_ID> --ipa <PATH> --version <VERSION>- Optional:
--wait,--submit --confirm,--platform,--poll-interval,--timeout
Manual sequence (when you need more control)
- Upload the build:
asc builds upload --app <APP_ID> --ipa <PATH>
- Find the build ID if needed:
asc builds latest --app <APP_ID> [--version <VERSION>] [--platform <PLATFORM>]
- TestFlight distribution:
asc builds add-groups --build <BUILD_ID> --group <GROUP_ID>[,<GROUP_ID>]
- App Store attach + submit:
asc versions attach-build --version-id <VERSION_ID> --build <BUILD_ID>asc submit create --app <APP_ID> --version <VERSION> --build <BUILD_ID> --confirm
- Check or cancel submission:
asc submit status --id <SUBMISSION_ID>or--version-id <VERSION_ID>asc submit cancel --id <SUBMISSION_ID> --confirm
macOS Release
macOS apps are distributed as .pkg files, not .ipa.
Build and Export
See asc-xcode-build skill for full build/archive/export workflow.
Upload PKG
Upload the exported .pkg using asc:
asc builds upload \
--app <APP_ID> \
--pkg <PATH_TO_PKG> \
--version <VERSION> \
--build-number <BUILD_NUMBER> \
--waitNotes:
--pkgautomatically sets platform toMAC_OS.asc publish appstorecurrently supports--ipaworkflows; for macOS.pkg, useasc builds upload --pkg+ attach/submit steps below.
Attach and Submit
Same as iOS, but use --platform MAC_OS:
# Wait for build to process
asc builds list --app <APP_ID> --platform MAC_OS --limit 5
# Attach to version
asc versions attach-build --version-id <VERSION_ID> --build <BUILD_ID>
# Create submission
asc review submissions-create --app <APP_ID> --platform MAC_OS
# Add version item
asc review items-add \
--submission <SUBMISSION_ID> \
--item-type appStoreVersions \
--item-id <VERSION_ID>
# Submit
asc review submissions-submit --id <SUBMISSION_ID> --confirmvisionOS / tvOS Release
Same as iOS flow, use appropriate --platform:
VISION_OSTV_OS
Multi-Platform Release
When releasing the same version across platforms:
- Upload each platform's build separately
- Create version for each platform if not exists
- Attach builds to respective versions
- Submit each platform separately (or together via reviewSubmissions API)
Pre-submission Checklist
Before submitting, verify:
- Build status is
VALID(not processing) - Encryption compliance resolved
- Content rights declaration set
- Copyright field populated
- All localizations complete
- Screenshots present
See asc-submission-health skill for detailed preflight checks.
Notes
- Always use
--helpto verify flags for the exact command. - Use
--output table/--output markdownfor human-readable output; default is JSON. - macOS builds require
ITSAppUsesNonExemptEncryptionin Info.plist to avoid encryption issues.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

