asc-release-flowEnd-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.
Install via ClawdBot CLI:
clawdbot install rudrankriyam/asc-release-flowUse this skill when you need to get a new build into TestFlight or submit to the App Store.
asc auth login or ASC_* env vars).ASC_APP_ID or pass --app explicitly.asc publish testflight --app --ipa --group [,] --wait, --notify, --platform, --poll-interval, --timeoutasc publish appstore --app --ipa --version --wait, --submit --confirm, --platform, --poll-interval, --timeoutasc builds upload --app --ipa asc builds latest --app [--version ] [--platform ] asc builds add-groups --build --group [,] asc versions attach-build --version-id --build asc submit create --app --version --build --confirm asc submit status --id or --version-id asc submit cancel --id --confirm --help to verify flags for the exact command.--output table / --output markdown for human-readable output; default is JSON.Generated Mar 1, 2026
A software development team needs to distribute a new iOS app build to internal testers via TestFlight for quality assurance. This scenario involves uploading an IPA file, assigning it to specific tester groups, and monitoring the distribution process to ensure timely feedback before App Store submission.
A company is preparing to launch an iOS app update on the App Store. This scenario requires uploading the build, attaching it to a specific version, and creating a submission with confirmation to meet Apple's review guidelines and schedule the release date.
An organization uses automated CI/CD pipelines to streamline iOS app releases. This scenario integrates asc commands into scripts to automatically upload builds, distribute to TestFlight for staging, and submit to the App Store upon successful tests, reducing manual effort.
A developer managing iOS and tvOS versions of an app needs to handle releases for different platforms. This scenario involves using platform-specific flags in asc commands to upload builds, manage versions, and submit to respective App Store categories efficiently.
Companies offering subscription-based mobile apps use this skill to regularly push updates and new features to users. It supports frequent TestFlight distributions for beta testing and App Store submissions to maintain service quality and user retention.
Developers of freemium apps rely on this skill to distribute free versions via TestFlight for user feedback and submit paid upgrades to the App Store. It helps manage build versions and submissions to optimize conversion rates and in-app purchases.
Businesses providing custom iOS apps for internal or client use utilize this skill for controlled TestFlight distributions to employees and App Store submissions for public releases. It ensures secure, versioned deployments aligned with corporate policies.
💬 Integration Tip
Integrate asc commands into CI/CD tools like Jenkins or GitHub Actions for automated build uploads and submissions, using environment variables for credentials to enhance security and streamline workflows.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.
Automated GitHub PR code review with diff analysis, lint integration, and structured reports. Use when reviewing pull requests, checking for security issues,...
Essential Git commands and workflows for version control, branching, and collaboration.
Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.
Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.