app-store-changelog
Generate user-facing App Store release notes from git history since the last tag.
Best use case
app-store-changelog is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate user-facing App Store release notes from git history since the last tag.
Teams using app-store-changelog should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/app-store-changelog/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How app-store-changelog Compares
| Feature / Agent | app-store-changelog | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate user-facing App Store release notes from git history since the last tag.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# App Store Changelog ## Overview Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes. ## When to Use - When the user asks for App Store "What's New" text or release notes from git history. - When you need to turn raw commits into concise, user-facing release bullets. ## Workflow ### 1) Collect changes - Run `scripts/collect_release_changes.sh` from the repo root to gather commits and touched files. - If needed, pass a specific tag or ref: `scripts/collect_release_changes.sh v1.2.3 HEAD`. - If no tags exist, the script falls back to full history. ### 2) Triage for user impact - Scan commits and files to identify user-visible changes. - Group changes by theme (New, Improved, Fixed) and deduplicate overlaps. - Drop internal-only work (build scripts, refactors, dependency bumps, CI). ### 3) Draft App Store notes - Write short, benefit-focused bullets for each user-facing change. - Use clear verbs and plain language; avoid internal jargon. - Prefer 5 to 10 bullets unless the user requests a different length. ### 4) Validate - Ensure every bullet maps back to a real change in the range. - Check for duplicates and overly technical wording. - Ask for clarification if any change is ambiguous or possibly internal-only. ## Commit-to-Bullet Examples The following shows how raw commits are translated into App Store bullets: | Raw commit message | App Store bullet | |---|---| | `fix(auth): resolve token refresh race condition on iOS 17` | • Fixed a login issue that could leave some users unexpectedly signed out. | | `feat(search): add voice input to search bar` | • Search your library hands-free with the new voice input option. | | `perf(timeline): lazy-load images to reduce scroll jank` | • Scrolling through your timeline is now smoother and faster. | Internal-only commits that are **dropped** (no user impact): - `chore: upgrade fastlane to 2.219` - `refactor(network): extract URLSession wrapper into module` - `ci: add nightly build job` ## Example Output ``` What's New in Version 3.4 • Search your library hands-free with the new voice input option. • Scrolling through your timeline is now smoother and faster. • Fixed a login issue that could leave some users unexpectedly signed out. • Added dark-mode support to the settings screen. • Improved load times when opening large photo albums. ``` ## Output Format - Title (optional): "What's New" or product name + version. - Bullet list only; one sentence per bullet. - Stick to storefront limits if the user provides one. ## Resources - `scripts/collect_release_changes.sh`: Collect commits and touched files since last tag. - `references/release-notes-guidelines.md`: Language, filtering, and QA rules for App Store notes. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
storerocket-automation
Automate Storerocket tasks via Rube MCP (Composio). Always search tools first for current schemas.
storeganise-automation
Automate Storeganise tasks via Rube MCP (Composio). Always search tools first for current schemas.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
wiki-changelog
Generate structured changelogs from git history. Use when user asks "what changed recently", "generate a changelog", "summarize commits" or user wants to understand recent development activity.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
context-management-context-restore
Use when working with context management context restore
code-refactoring-context-restore
Use when working with code refactoring context restore
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
app-store-optimization
Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".