release

Prepare and publish an Apple app release with versioning and GitHub release creation.

1|Updated Feb 28, 2026

Search Tags:#automation #github #release #semver #apple #ci

Ready to run

npx skills add https://github.com/glwr/ai-coding-base --skill release-glwr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/glwr/ai-coding-base/tree/main/apple/.claude/skills/release
Command: npx skills add https://github.com/glwr/ai-coding-base --skill release-glwr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing an Apple app involves many manual steps—running pre‑release checks, deciding the correct SemVer bump, tagging the repo, creating a GitHub Release, and updating issue tracking and documentation. This Skill automates the entire flow so teams can reliably ship releases without missing critical steps.

Core Features & Use Cases

Pre‑Release Validation: Ensures all features are complete, tests pass, and no critical bugs remain.
Semantic Version Determination: Analyzes issue labels and commits to suggest the appropriate MAJOR, MINOR, or PATCH bump.
Automated Tagging & Release Creation: Creates a signed Git tag, pushes it, and generates a GitHub Release with auto‑generated notes.
Tracking Updates: Marks related issues as done, updates feature indexes, closes milestones, and syncs documentation.
First‑Release Setup: Guides initial configuration of App Store Connect, certificates, and branch protection.

Quick Start

Ask the release skill to prepare version v1.2.0 and publish the GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate Apple app release versioning and publishing with GitHub?▼

Automating Apple app release versioning and publishing requires handling pre-release validation, SemVer bump determination, Git tagging, and GitHub Release creation. This Skill operates on a completed milestone or set of issue numbers, analyzing commits and labels to suggest the appropriate MAJOR, MINOR, or PATCH version bump before pushing a signed tag.

How does semantic version determination work for iOS app releases?▼

Semantic version determination for iOS app releases analyzes issue labels and commits within a completed milestone to suggest the appropriate MAJOR, MINOR, or PATCH bump. This ensures the version number accurately reflects the scope of changes made since the last release, preventing manual misclassification of version increments.

Can I use GitHub CLI to automate pre-release validation for Apple apps?▼

Yes, you can use GitHub CLI to automate pre-release validation for Apple apps. This Skill requires access to git, GitHub CLI, and project documentation such as README and feature specs to verify readiness. It ensures all features are complete, tests pass, and no critical bugs remain before proceeding with the release.

What is the best way to manage Apple app release tracking and milestone closures?▼

Managing Apple app release tracking and milestone closures is best handled by automating the update of tracking artifacts. After publishing a GitHub Release, this Skill automatically marks related issues as done, updates feature indexes, closes the associated milestone, and syncs project documentation to reflect the newly shipped version.

Do I need App Store Connect configuration to prepare a GitHub release for an Apple app?▼

You do not need App Store Connect configuration strictly for GitHub release creation, but it is required for first-release setup. This Skill can guide the initial configuration of App Store Connect, certificates, and branch protection, ensuring both the Git repository and Apple publishing environments are prepared for deployment.

Why does automated Apple app releasing require access to feature specs and context files?▼

Automated Apple app releasing requires access to feature specs and context files to verify release readiness. By reading project documentation like READMEs and feature specs alongside issue labels, the Skill ensures that all defined features are actually complete and validated before determining the SemVer bump and pushing a Git tag.