agentleFS
Sign inStart free
VelimirMuellerVelimirMueller/ai-development-skills/skills/swift/app-store-changelog/SKILL.md

app-store-changelog

Skill7 starsChanged 18 days agoMITView on GitHub

Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags. Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref).

11 other projects use a version of this, 10 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use gh-issue-fix-flow, swiftui-liquid-glass and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ParkerRexSkill

    gh-issue-fix-flow

    End-to-end GitHub issue fix workflow using gh, local code changes, builds/tests, and git push. Use when asked to take an issue number, inspect the issue via gh, implement a fix, run XcodeBuildMCP builds/tests, commit with a closing message, and push.

    Also in 3 projects that use this

  • OpenAISkill

    swiftui-liquid-glass

    Implement and review iOS 26+ SwiftUI Liquid Glass UI. Use when adopting Liquid Glass or checking its correctness, performance, and design fit.

    Also in 4 projects that use this

  • OpenAISkill

    ios-debugger-agent

    Build, run, and debug iOS apps on Simulator with XcodeBuildMCP. Use when launching an app, inspecting simulator UI or logs, or diagnosing runtime behavior.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

9 rules. 7 are common, 0 are distinctive, and 2 are very specific to this project.

  • 7

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run scripts/collect_release_changes.sh from the repo root to gather commits and touched files.

    line 14
  2. Very specific:

    If needed, pass a specific tag or ref: scripts/collect_release_changes.sh v1.2.3 HEAD.

    line 15
  3. Common:

    If no tags exist, the script falls back to full history.

    line 16
  4. Common:

    Write short, benefit-focused bullets for each user-facing change.

    line 24
  5. Common:

    Use clear verbs and plain language.

    line 25
  6. Common:

    Prefer 5 to 10 bullets unless the user requests a different length.

    line 26
  7. Common:

    Ensure every bullet maps back to a real change in the range.

    line 29
  8. Common:

    Check for duplicates and overly technical wording.

    line 30
  9. Common:

    Ask for clarification if any change is ambiguous or possibly internal-only.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free