App Store Changelog

SkillDocs & knowledge

app-store-changelog is a skill that turns git history into App Store release notes. It collects commits and changed files since the last tag, filters out internal-only work like CI jobs and refactors, and drafts short, user-facing What's New bullets grouped under New, Improved, and Fixed themes.

Use App Store Changelog in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add App Store Changelog and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the App Store Changelog skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Have a git repository with commit history; tags are optional since the script falls back to full history without them.

App Store ChangelogStart free

What your AI can do with it

  • Runs scripts/collect_release_changes.sh to gather commits and touched files since
  • Accepts a specific tag or ref, such as scripts/collect_release_changes.sh v1.2.3 HEAD
  • Falls back to full history when no tags exist
  • Drops internal-only commits such as dependency bumps, refactors, and CI changes
  • Groups user-visible changes into New, Improved, and Fixed bullets
  • Validates that every bullet maps back to a real commit before output

Getting started

  1. Have a git repository with commit history; tags are optional since the script falls back to full history without them.
  2. Add the app-store-changelog skill to your agent's available skills.
  3. Ask the agent for App Store release notes or What's New text from git history.
  4. Optionally give a specific tag or ref to define the range, and a storefront character limit if you have one.
  5. Review the drafted bullets and ask for changes to length, wording, or grouping.

What this skill tells your AI

The instructions your AI receives, as published by sickn33/agentic-awesome-skills in skills/app-store-changelog/SKILL.md and read by ahel’s review.

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 messageApp 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.

Signals

GitHub stars
47k
Forks
7k
Last commit
Sep 2026

ahel review

  • K6low
    bundled executables the agent is told to run

Automated review, not a security audit. Ruleset v1+k2.

Others that do the same job

Questions

What if the repository has no tags?
The collection script falls back to using the full commit history when no tags exist.
Can I generate notes for a specific version range?
Yes. Pass a specific tag or ref to the script, for example scripts/collect_release_changes.sh v1.2.3 HEAD.
Does it filter out internal commits?
Yes. Build scripts, refactors, dependency bumps, and CI changes are dropped so only user-visible changes become bullets.
Advanced
Item type
skill
Key
app-store-changelog-sickn33
Source
github.com/sickn33/agentic-awesome-skills