archive

Archive, version bump, and upload iOS apps to TestFlight via App Store Connect.

2|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/rfhayn/forager --skill archive-rfhayn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archive
Source: https://github.com/rfhayn/forager/tree/main/.claude/skills/archive
Command: npx skills add https://github.com/rfhayn/forager --skill archive-rfhayn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires xcodebuild, git, appstore-connect, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of archiving, version bumping, and distributing an iOS app to TestFlight, streamlining the release workflow.

Core Features & Use Cases

  • Automated App Distribution: Automates the entire process of archiving, uploading, and distributing an iOS app to TestFlight.
  • Version Bumping: Automatically increments the build number for each release.
  • Upload to App Store Connect: Uploads the archived app to App Store Connect.
  • TestFlight Distribution: Distributes the app to TestFlight beta testers.
  • Use Case: For developers looking to automate their app release process and ensure that the latest version is always available to testers.

Quick Start

Run the 'archive' command to distribute the app to TestFlight.

Frequently Asked Questions about archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate iOS app distribution to TestFlight?

Automating iOS app distribution to TestFlight is achieved by archiving the app, bumping the build version, and uploading to App Store Connect. This workflow requires Xcode build tools and App Store Connect API access to ensure the latest version reaches beta testers.

How do I automatically increment the build number for iOS TestFlight releases?

Automatically incrementing the build number for iOS TestFlight releases is handled during the archiving process. The workflow bumps the version number before uploading the archived app to App Store Connect, ensuring each distributed build is uniquely versioned.

Does automating TestFlight uploads require App Store Connect API access?

Automating TestFlight uploads does require App Store Connect API access. The distribution process depends on the appstore-connect dependency to upload the archived iOS application and deploy it to beta testers seamlessly.

What is the best way to manage iOS release workflows using xcodebuild and git?

The best way to manage iOS release workflows is to automate the archiving, version bumping, and uploading steps. By integrating xcodebuild and git, the process archives the app, increments the build number, and uploads to App Store Connect for TestFlight distribution.

Can I distribute an iOS app to beta testers without manual Xcode archiving?

Distributing an iOS app to beta testers without manual Xcode archiving is possible through automated release management. The process leverages xcodebuild to archive, bumps the version, and uploads directly to App Store Connect for TestFlight distribution.

Why are my automated TestFlight uploads failing during the App Store Connect upload phase?

Automated TestFlight uploads typically fail due to incorrect App Store Connect API access or missing Xcode build tools. The distribution process requires valid API credentials and a properly configured Xcode environment to archive and upload the iOS app successfully.