app-store-changelog

Collect git history changes and draft App Store release notes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dereknex/skills --skill app-store-changelog-dereknex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-store-changelog
Source: https://github.com/dereknex/skills/tree/main/app-store-changelog
Command: npx skills add https://github.com/dereknex/skills --skill app-store-changelog-dereknex

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Turn git history into user-facing App Store release notes, reducing manual drafting and ensuring consistent, customer-friendly messaging.

Core Features & Use Cases

  • Collect changes since the last tag or a specified ref using the dedicated script from the repository root.
  • Triaging changes by user impact and grouping them into themes like New, Improved, and Fixed.
  • Drafting concise, benefit-focused bullets suitable for App Store notes and marketing materials.
  • Validating that every bullet maps to a real change to prevent internal-only or unclear items.

Quick Start

Run the release notes workflow from the repository root to collect changes and generate a publish-ready notes draft.

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

Yes, you can generate App Store release notes from git history by collecting commits since a specified ref, grouping touched files by user impact, and drafting concise, customer-friendly bullets validated against real changes.

What's the best way to group git commits into themes for a changelog?

Group git commits into changelog themes by collecting touched files and commit history, then triaging changes by user impact into categories like New, Improved, and Fixed to produce benefit-focused, publish-ready bullets.

Do I need git installed to create App Store release notes with this workflow?

Yes, git is a required dependency. The workflow runs from the repository root and uses git to collect commit history and touched files since the last tag or a specified ref to draft the release notes.

How does validating release notes against real git changes prevent unclear items?

Validating release notes against real git changes ensures every drafted bullet maps to an actual commit and touched file, preventing internal-only, technical, or unclear items from appearing in user-facing App Store notes.

Can I specify a custom git ref instead of the last tag for collecting changes?

Yes, you can specify a custom git ref instead of the last tag. The workflow collects commit history and touched files starting from that specified ref to group changes by theme and draft the App Store release notes.

Why should I use an automated changelog generator for App Store marketing assets?

Use an automated changelog generator to reduce manual drafting effort and ensure consistent, customer-friendly messaging across App Store notes and marketing materials by translating raw git history into validated, user-facing bullets.