Generate App Store release notes from git history

App Store Changelog generates a comprehensive, user-facing changelog from git history since the last tag, then translates commits into clear App Store release notes. It runs scripts/collect_release_changes.sh from the repo root to gather commits and touched files, optionally with a specific tag or ref range (falling back to full history if no tags exist).

It then triages for user impact: scanning commits and touched files to identify user-visible changes, grouping them by theme (New, Improved, Fixed), deduplicating overlaps, and dropping internal-only work such as build scripts, refactors, dependency bumps or CI changes. It drafts short, benefit-focused bullets for each user-facing change using clear verbs and plain language, avoiding internal jargon, and preferring 5 to 10 bullets unless a different length is requested. It validates the result by checking that every bullet maps back to a real change in the range, checking for duplicates or overly technical wording, and asking for clarification when a change is ambiguous or possibly internal-only.

Worked translation examples: fix(auth): resolve token refresh race condition on iOS 17 becomes "Fixed a login issue that could leave some users unexpectedly signed out"; feat(search): add voice input to search bar becomes "Search your library hands-free with the new voice input option"; perf(timeline): lazy-load images to reduce scroll jank becomes "Scrolling through your timeline is now smoother and faster." Commits it drops as having no user impact include dependency version bumps, internal module refactors, and CI job additions.

The output is 5-10 bullets, one sentence each starting with a verb, with no internal codenames, ticket IDs or file paths. Filtering includes new features, UI/behavior changes, user-noticeable bug fixes and visible performance improvements, and excludes refactors, dependency bumps, CI changes, and internal logging or analytics changes unless they affect user privacy or behavior. Technical terms are translated into user-facing wording, words like "API", "refactor", "nil", "crash log" or "dependency" are avoided, and verbs like "Added", "Improved", "Fixed" and "Updated" are preferred.

Use it when the user asks for App Store "What's New" text or release notes from git history, or needs raw commits turned into concise, user-facing release bullets. Use it only when the task clearly matches this scope; stop and ask for clarification if required inputs, permissions, safety boundaries or success criteria are missing, and do not treat the output as a substitute for environment-specific validation, testing or expert review.

Input is a git repository with tags (or full history if none exist) and an optional since/until ref range. Output is a bullet-list "What's New" changelog, grouped by theme if needed, with each bullet mapped to a real user-facing change and internal-only commits dropped.

It suits app developers and release managers who need App Store release notes generated from raw git history rather than written from scratch.