ship-ios-app

Automate iOS and macOS release readiness checks and shipping workflows.

5|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/intrusive-memory/skills --skill ship-ios-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-ios-app
Source: https://github.com/intrusive-memory/skills/tree/main/ship-ios-app
Command: npx skills add https://github.com/intrusive-memory/skills --skill ship-ios-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release workflow for iOS and macOS apps distributed via App Store Connect, helping teams ship builds faster with fewer errors.

Core Features & Use Cases

  • Pre-flight Checks: Verify a ready PR, ensure version bumps, and confirm changelog entries before shipping.
  • Version & Changelog Consistency: Compare documentation versions with the last tag to prevent mismatches.
  • Shipping Process: Squash merge PR, update local and remote state, tag, and publish a release with a clear audit trail.
  • Verification & Reporting: Validate tag existence and share a shipment summary.

Quick Start

Ship the latest PR to main by telling Claude: "Ship PR #42 for my App." This initiates pre-flight checks, merges the PR, bumps the version, creates a tag, and publishes a release.

Frequently Asked Questions about ship-ios-app

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

FAQPage Schema
How do I automate iOS app releases to the App Store?

Automate iOS app releases by using pre-flight checks to verify PR readiness, version bumps, and changelog entries, then squash merge, tag, and publish to App Store Connect. This eliminates manual coordination and ensures consistency between your codebase and App Store metadata.

What checks happen before shipping an iOS app release?

Pre-flight checks verify that a PR targets main, version numbers match documentation, changelog entries exist, marketing and build numbers align, and App Store Connect metadata is consistent. These checks prevent shipping incomplete or mismatched releases.

Can I automate version bumping and tagging for macOS releases?

Yes. The release workflow automatically handles version bumping in documentation, creates git tags, and pushes changes for both iOS and macOS apps distributed via App Store Connect, enforcing alignment between local state and remote repositories.

Do I need a specific Git workflow for automated app releases?

You need a PR targeting main with a version bump in documentation and a changelog entry. The automation squash merges the PR, validates App Store consistency, tags the release, and generates an audit trail—no manual git commands required.

What happens after an app release is published?

Post-release reporting validates tag existence and shares a shipment summary, providing a clear audit trail of what was shipped, when it was tagged, and confirmation that the release reached App Store Connect.

How do I prevent version mismatches between documentation and App Store?

Pre-flight verification compares documentation versions with the last git tag and validates App Store version metadata before merging. This catches mismatches before the PR is shipped, ensuring single source of truth.