app-store-changelog — Claude Code skill: release notes from git
Turns commits since your last tag into App Store “What's New” copy. Handy right before you ship a build to the store.
npx skills add Dimillian/Skills --skill app-store-changelog -a claude-codeWhat app-store-changelog does
The skill walks your git history from the last tag up to HEAD and pulls out whatever a user would notice. A script, scripts/collect_release_changes.sh, does the gathering: run it from the repo root and it returns commits plus the files they touched. Want a narrower window? Pass a range, as in scripts/collect_release_changes.sh v1.2.3 HEAD. With no tags in the repo, the script reads the whole history instead.
Then comes triage. Build scripts, refactors, dependency bumps and CI work get dropped, and what survives is grouped under New, Improved and Fixed with overlaps merged. The output is short bullets about the benefit to a person, no internal jargon. It suggests 5 to 10 bullets unless you ask for another length. A second file, references/release-notes-guidelines.md, holds the language and QA rules.
There is also a table showing how a raw commit message becomes a store bullet. That matters when your team writes commits for itself rather than for users. One caveat: with no tags to anchor the range, the skill ends up summarising the entire project, so tag your previous release before running it.
What it helps with
- draft “What's New” copy from commits before a release
- separate user-facing changes from refactors and CI
- group changes under New, Improved and Fixed
- merge duplicate entries across commits and files
- rewrite technical commit messages in plain language
Example prompts for the agent
- Generate App Store release notes since the last tag
- Collect changes between
v1.2.3andHEADand turn them into What's New text - Write 6 bullets for the new version, only things users will notice
How to install app-store-changelog
1Skills CLI (Vercel)
npx skills add Dimillian/Skills --skill app-store-changelog -a claude-code2Manually: put the files in place
~/.claude/skills/app-store-changelog/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/app-store-changelog/
1Skills CLI (Vercel)
npx skills add Dimillian/Skills --skill app-store-changelog -a codex2Manually: put the files in place
.agents/skills/app-store-changelog/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Dimillian/Skills --skill app-store-changelog -a cursor2Manually: put the files in place
.cursor/skills/app-store-changelog/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Dimillian/Skills app-store-changelog2Manually: put the files in place
.github/skills/app-store-changelog/SKILL.md1Skills CLI (Vercel)
npx skills add Dimillian/Skills --skill app-store-changelog -a gemini-cli2Platform CLI
gemini skills install https://github.com/Dimillian/Skills --path app-store-changelogManually: put the files in place
.devin/skills/app-store-changelog/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Dimillian/Skills --skill app-store-changelog -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about app-store-changelog
How do I install app-store-changelog in Claude Code?
Run npx skills add Dimillian/Skills --skill app-store-changelog -a claude-code. The skill file lands at ~/.claude/skills/app-store-changelog/SKILL.md.
What does app-store-changelog do?
It reads git history since the last tag, keeps only user-visible changes and writes them as short store bullets. Internal commits such as build tweaks and dependency bumps are discarded.
What do I need for the skill to work?
A git repo with history and a tag marking the previous release. You can pass a range yourself, and if no tags exist the script falls back to the full history.
Source text
SKILL.md · MIT
--- name: app-store-changelog description: Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags. --- # 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. ## 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.
© Dimillian · MIT · Dimillian/Skills