ship-swift-library

Automate Swift library releases by merging PRs, bumping versions, and publishing GitHub releases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end process of releasing Swift libraries by ensuring PRs are merged correctly, version bumps are applied, and releases are published from the PR merge commit.

Core Features & Use Cases

  • PR-first release flow: Merge an open PR from development to main before releasing.
  • CI checks orchestration: Verify that all required CI checks pass before release.
  • Version bump automation: Increment library version in the source file following semantic versioning.
  • Release tagging and publishing: Create annotated tags from the PR merge commit and publish GitHub releases.
  • Audit trail: Generate descriptive commit messages and release notes for traceability.

Quick Start

Trigger the release flow on the open PR from development to main. The skill will merge the PR, verify CI, bump the version, tag, and publish a GitHub release from the PR merge commit.

Frequently Asked Questions about ship-swift-library

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

FAQPage Schema
How do I automate Swift library releases with version bumps and GitHub tags?

This Skill automates end-to-end Swift library releases by merging development PRs to main, bumping semantic versions, creating annotated tags, and publishing GitHub releases in a single workflow. It enforces CI checks and produces a squash-merged commit with corresponding release artifacts.

Can I automate merging PRs and publishing releases without manual steps?

Yes. The Skill merges development-to-main PRs after verifying CI checks pass, automatically increments the version in your source file, tags the merge commit, and creates a GitHub release—eliminating manual coordination between steps.

What happens if CI checks fail during the release workflow?

The Skill verifies all required CI checks pass before proceeding. If checks fail, the PR merge and subsequent release steps do not execute, preserving main branch integrity and preventing broken releases.

How does this approach differ from manual release processes?

Manual releases require separate steps: merging PRs, editing version files, creating tags, and publishing releases. This Skill orchestrates all operations through Git and GitHub CLI commands in sequence, reducing human error and ensuring consistent audit trails.

What version control setup do I need before using this Skill?

You need an open pull request from a development branch to main, Git and GitHub CLI installed, and a Swift source file containing the version string. The Skill updates the version file, so write permissions to main are required.

Can I use this Skill with Swift packages on GitHub?

Yes. The Skill works with any Swift library on GitHub that follows a development-to-main PR workflow. It uses standard Git commands and GitHub CLI operations compatible with Swift package structures and semantic versioning.