asc-shots-pipeline
Orchestrate iOS screenshot automation from build through frame composition to App Store Connect upload.
- Build and launch apps on simulators with Xcode CLI tools, then drive UI interactions and capture screenshots using AXe plan files
- Frame screenshots deterministically with pinned Koubou 0.14.0, supporting six device types (iPhone Air, iPhone 17 Pro, iPhone 17 Pro Max, iPhone 16e, iPhone 17, Mac)
- Configure pipelines via JSON settings and capture plans; skip framing or upload stages as needed
- Capture multi-locale screenshots in parallel by mapping locales to dedicated simulator UDIDs, then batch-frame and upload to App Store Connect with per-locale version localization IDs
asc screenshots pipeline (xcodebuild -> AXe -> frame -> asc)
Use this skill for agent-driven screenshot workflows where the app is built and launched with Xcode CLI tools, UI is driven with AXe, and screenshots are uploaded with asc.
Current scope
- Implemented now: build/run, AXe plan capture, frame composition, and upload.
- Device discovery is built-in via
asc screenshots list-frame-devices. - Local screenshot automation commands are experimental in asc cli.
- Framing is pinned to Koubou
0.18.1for deterministic output. - Feedback/issues: https://github.com/rorkai/App-Store-Connect-CLI/issues/new/choose
Defaults
- Settings file:
.asc/shots.settings.json - Capture plan:
.asc/screenshots.json - Raw screenshots dir:
./screenshots/raw - Framed screenshots dir:
./screenshots/framed - Default frame device:
iphone-air
1) Create settings JSON first
More from rudrankriyam/app-store-connect-cli-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.
2.3Kasc-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.
2.3Kasc-release-flow
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
2.2Kasc-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.
2.2Kasc-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.
2.2Kasc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
2.1K