app-store-changelog

The app-store-changelog skill automates the transformation of technical git history into human-readable release notes suitable for public storefronts. It functions by executing local scripts to extract commit data since the previous tag, filtering out internal infrastructure updates, build configurations, and refactoring noise. The skill categorizes the remaining commits into logical themes like new features, improvements, or bug fixes, and rephrases them into concise, benefit-driven bullets. By applying specific style guidelines for App Store submission, it ensures that your documentation remains approachable and avoids technical jargon that might confuse end users. This workflow removes the manual labor of tracking commits through git logs and drafting release copy from scratch, ensuring that your app updates accurately reflect what users will actually experience after installing the latest version.

When to Use This Skill

• •Preparing release notes for a monthly iOS app update
• •Drafting version history for a TestFlight distribution
• •Generating documentation for a public App Store patch release
• •Summarizing features for a new major version launch

How to Invoke This Skill

Example prompts that trigger this skill in Claude Code, Cursor, or Antigravity:

• “Draft my App Store release notes since the last tag
• “Generate a changelog based on the latest git history
• “Create user-friendly notes for version v1.2.4
• “Summarize what changed in the repo since the last release
• “Help me write release notes for the current build

Pro Tips

• 💡Adopt a consistent commit message convention (e.g., Conventional Commits) to improve the skill's ability to identify and categorize changes accurately.
• 💡Always ensure your releases are properly tagged in Git; the skill relies on these tags to define release boundaries effectively.
• 💡After generation, review and fine-tune the output for brand voice and specific marketing emphasis before publishing to the App Store.

What this skill does

• •Extracts git commit history relative to the last version tag
• •Filters out internal commits such as dependency bumps and build scripts
• •Categorizes changes into standardized release note groupings
• •Translates technical commit messages into user-facing copy
• •Validates generated text against storefront character constraints

When not to use it

• ✕Projects lacking consistent commit messaging standards
• ✕Repos where the git history does not correspond to user-visible changes
• ✕Situations requiring creative marketing copy beyond standard release notes

Example workflow

1. Run the collect_release_changes.sh script to pull raw commit data
2. Review the gathered commits to identify user-facing updates
3. Request a thematic grouping of features, improvements, and fixes
4. Draft bulleted release notes focusing on user benefits
5. Verify the output against App Store character limit guidelines
6. Finalize the copy for the submission portal

Prerequisites

• –Git history with version tags
• –The scripts/collect_release_changes.sh utility
• –references/release-notes-guidelines.md

Pitfalls & limitations

• !Requires clean commit messages to function effectively
• !May struggle to filter out significant internal architectural changes that lack clear labels
• !Does not inherently know about marketing goals or specific feature highlight priorities

FAQ

How it compares

Unlike manual drafting which is prone to oversight and inconsistency, this skill uses systematic filtering and predefined style guidelines to ensure your release notes are always accurate and adhere to store requirements.

Source & trust

Recommended Rules

Recommended Workflows

Recommended MCP Servers