app-store-changelog

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

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill app-store-changelog-curtislmartin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-store-changelog
Source: https://github.com/curtislmartin/daily-ascent-engineering/tree/main/skills_repo/app-store-changelog
Command: npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill app-store-changelog-curtislmartin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Generate user-facing App Store release notes by summarizing changes from git history since the most recent tag, helping teams publish clear What's New text without manual drafting.

Core Features & Use Cases

  • Collect commits and touched files since the last tag (or a specified ref).
  • Identify user-visible changes and translate them into concise bullets for App Store notes.
  • Draft release notes and validate them against common storefront guidelines, handling multiple releases if needed.

Quick Start

Run the release notes workflow to generate a user-facing App Store changelog from your git history.

Frequently Asked Questions about app-store-changelog

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

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

To auto-generate App Store release notes from git history, this Skill collects commits since the last tag, triages for user-visible changes, and drafts concise bullets validated against storefront guidelines. It translates technical git history into user-facing What's New text automatically.

What is the best way to create user-facing changelogs from git commits?

The best way to create user-facing changelogs from git commits is to summarize user-impacting changes since a specified reference point. This Skill triages repository history between your last tag and HEAD, yielding App Store style notes without manual drafting.

Does generating App Store release notes require existing git tags?

Generating App Store release notes does not strictly require existing git tags. If no tags are found, the Skill uses the full repository history from the beginning to HEAD, rather than failing or requiring manual reference point configuration.

Can I generate release notes for multiple app versions at once?

Yes, you can generate release notes for multiple releases when needed. The Skill handles multiple releases by drafting and validating user-facing App Store bullets against common storefront guidelines for each set of changes gathered from your git history.

What are the limitations of drafting App Store notes from git history?

A limitation of drafting App Store notes from git history is that the Skill requires a collection script to gather commits and triage for user-visible changes. It depends on git and operates between a last-tag reference and HEAD to yield valid storefront guidelines output.