app-store-changelog

Collect git history changes and format App Store release notes.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Pallepadehat/agentkit --skill app-store-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-store-changelog
Source: https://github.com/Pallepadehat/agentkit/tree/main/.agent/skills/app-store-changelog
Command: npx skills add https://github.com/Pallepadehat/agentkit --skill app-store-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps engineering and product teams generate user-facing App Store release notes by aggregating changes from git history since the last tag or a specified ref, translating them into clear, customer-facing bullets.

Core Features & Use Cases

  • Triage changes by user impact: identify feature additions, improvements, and fixes that users will notice.
  • Draft concise, compliant App Store notes automatically according to guidelines in the references/release-notes-guidelines.md.
  • Produce a ready-to-publish What’s New style list with 5 to 10 bullets, grouped by theme if needed.

Quick Start

Run scripts/collect_release_changes.sh from the repository root to gather commits and touched files since the last tag, then review the generated list to craft user-facing App Store 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 commit history?

Generate App Store release notes by running the collect_release_changes.sh script from your repository root. It aggregates commits since the last tag, identifies user-visible changes, and formats them into 5–10 customer-facing bullets following App Store guidelines.

Can I automate changelog creation for app store releases?

Yes. This Skill automates changelog creation by parsing git history, triaging changes by user impact, and producing ready-to-publish release notes that comply with App Store standards without manual formatting.

What makes commits translatable into user-facing release notes?

Release notes require filtering commits for user-visible changes—features, improvements, and fixes—rather than all technical commits. This Skill applies release-notes guidelines to distinguish customer-impacting work and craft concise, themed bullet points.

Do I need git history to create release notes?

Yes. This Skill depends on git and relies on commit history since the last tag or a specified ref. Your repository must contain tagged releases or a reference point to identify the scope of changes to include.

What's the difference between git commits and App Store changelog bullets?

Git commits are technical; App Store changelogs are customer-focused. This Skill bridges the gap by extracting user-impacting commits, removing jargon, grouping by theme, and formatting them into 5–10 polished bullets that users understand.

Can I customize the release notes format or guidelines?

Yes. The Skill references release-notes-guidelines.md, which you can modify to enforce your organization's tone, structure, and compliance standards for App Store or storefront submissions.