app-store-changelog

Name: app-store-changelog
Availability: InStock
Author: Michael Schuerig

Collect and summarize user-impacting git changes into App Store release notes.

Updated Feb 11, 2026

Search Tags:#automation #changelog #app-store #release-notes #git-history #bullets

Ready to run

npx skills add https://github.com/mschuerig/peach-ios --skill app-store-changelog-mschuerig

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: app-store-changelog
Source: https://github.com/mschuerig/peach-ios/tree/main/.agents/skills/app-store-changelog
Command: npx skills add https://github.com/mschuerig/peach-ios --skill app-store-changelog-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate clear, user-facing App Store release notes by collecting and summarizing user-impacting changes since the last git tag (or a specified ref), enabling teams to communicate updates effectively to users.

Core Features & Use Cases

Collect changes from git history since the last tag or a specified ref.
Triages and surfaces user-visible changes, filtering out internal work.
Draft concise, storefront-ready bullets that align with App Store guidelines for release notes.

Quick Start

Run the app-store-changelog workflow against your repository to draft the release notes.

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?▼

Generate App Store release notes by collecting and summarizing user-impacting git changes since the last tag. The workflow translates commits into clear, user-facing bullets aligned with App Store guidelines.

Can I generate release notes from a specific git ref instead of the last tag?▼

Yes, you can generate release notes from a specific git ref. The workflow supports optional ref ranges for targeted releases, allowing you to collect changes from a specified reference point rather than just the last tag.

How are internal commits filtered out of app store changelogs?▼

Internal commits are filtered out by triaging and surfacing only user-visible changes from the git history. This ensures the final app store changelog contains concise, storefront-ready bullets relevant to end users.

Do I need any dependencies to turn git history into release notes?▼

No dependencies are required to turn git history into release notes. The workflow operates independently to collect git changes and draft compliant App Store release notes directly from your repository.

What is the best way to write user-facing bullets from git commits for app releases?▼

The best way to write user-facing bullets from git commits is to summarize user-impacting changes since the last tag. This workflow drafts concise, storefront-ready release notes that align with App Store guidelines.