app-store-changelog

Generate App Store release notes from git history since the last tag.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Roy-wonji/claude-config --skill app-store-changelog-roy-wonji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-store-changelog
Source: https://github.com/Roy-wonji/claude-config/tree/main/skills/app-store-changelog
Command: npx skills add https://github.com/Roy-wonji/claude-config --skill app-store-changelog-roy-wonji

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps you quickly create user-facing App Store “What’s New” release notes without manually reading every commit or guessing which changes are actually visible to users.

Core Features & Use Cases

  • Auto-collects changes from git history: Gathers commits and touched files since the last tag (or a specified ref) to build a reliable change set for release notes.
  • Filters for user-impacting work: Triages commits to keep benefits and fixes while dropping internal-only items like refactors, dependency bumps, and CI changes.
  • Translates commits into storefront-ready bullets: Produces short, plain-language, one-sentence-per-bullet notes you can paste into App Store Connect.
  • Use case: Preparing release notes for a new version by summarizing all user-relevant changes since the previous release, including improvements and bug fixes.

Quick Start

Ask the AI to generate App Store “What’s New” notes for your app using the changes since the last git tag.

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 from git history by running a release-collection script that gathers commits and touched files since a specified tag, then summarizing user-impacting changes into short, benefit-focused bullets for your storefront.

How do I filter internal-only commits when creating release notes?

Filter internal-only commits during release note generation by triaging the collected git history to drop refactors, dependency bumps, and CI changes, keeping only fixes and benefits that are actually visible to users.

What is the best way to write What's New drafts for App Store Connect?

The best way to write What's New drafts for App Store Connect is to summarize user-relevant changes from commit ranges into plain-language, one-sentence-per-bullet notes that highlight user benefits and bug fixes.

Can I generate a comprehensive changelog from a specific commit range?

Yes, you can generate a comprehensive changelog from a specific commit range by providing a specified git ref or tag to the collection script, which gathers all touched files and commits to build a validated change set.

Do I need a specific git branch or tag structure to automate release note creation?

You need a git repository with existing tags or refs to automate release note creation, as the script collects commits and file changes starting from the last tag or a specified ref to establish the baseline for summarization.

Why should I use automated git history summarization instead of manually writing release notes?

Automated git history summarization prevents you from manually reading every commit and guessing user impact, reliably extracting storefront-ready bullets by validating touched files against the selected release range to ensure accuracy.