app-store-changelog

Generates App Store release notes by summarizing user-facing git commits since the last tag.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill app-store-changelog-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-store-changelog
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/app-store-changelog
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill app-store-changelog-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Writing App Store "What's New" text from raw git history is tedious and error-prone. This Skill collects commits since the last tag, filters out internal-only work, and translates technical commit messages into clear, benefit-focused release notes. ## Core Features & Use Cases - Automated Change Collection: Runs a shell script to gather commits and touched files since the last git tag or a specified ref, with fallback to full history when no tags exist. - User-Impact Triage: Groups changes into New, Improved, and Fixed themes while dropping internal-only work like refactors, dependency bumps, and CI changes. - Storefront-Ready Output: Produces 5-10 plain-language bullets that map back to real changes and respect App Store text limits. - Use Case: Before shipping version 3.4 of an iOS app, run the Skill to turn dozens of raw commits into a polished "What's New" section ready to paste into App Store Connect. ## Quick Start Generate App Store release notes for all changes since the last git tag in this repository.

Frequently Asked Questions about app-store-changelog

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

FAQPage Schema
How do I generate App Store release notes from git history?▼

Run the collect_release_changes.sh script from the repo root to gather commits since the last tag, then triage them for user impact and rewrite each user-facing change as a short, benefit-focused bullet. Internal-only commits like refactors and CI changes are dropped.

How to write What's New text for an iOS app release?▼

Write 5 to 10 one-sentence bullets that start with verbs like Added, Improved, or Fixed, and describe visible benefits rather than technical details. Avoid jargon such as API, refactor, or dependency, and group changes by New, Improved, and Fixed themes.

Can I generate release notes from a specific git tag or ref?▼

Yes, pass a tag or ref as arguments to the script, for example collect_release_changes.sh v1.2.3 HEAD, to define the commit range. If no tags exist in the repository, the script falls back to the full commit history.

What commits should be excluded from App Store release notes?▼

Exclude internal-only work such as refactors, dependency bumps, CI changes, developer tooling, and internal logging. Include only changes users would notice: new features, UI updates, bug fixes, and visible performance improvements.

Why do my release notes include commits with no user impact?▼

This happens when triage is skipped and raw commits are copied directly. Review each commit against the filtering rules, drop internal-only work, and ask for clarification when a change is ambiguous or possibly invisible to users.