mcpField
A
app-store-changelog

app-store-changelog

github.com/sickn33Marketing & growth48.7k61 installsUpdated 1d ago
Repository

About app-store-changelog

app-store-changelog is a skill for turning Git history into user-facing App Store release notes, for teams preparing version updates. It filters user-visible changes, groups them by theme, and calls for checking each claim against actual changes.

Key features

  1. 01Collect commits and changed files since a tag
  2. 02Filter and group user-visible changes
  3. 03Draft release-note bullets from changes
  4. 04Verify notes against actual changes

Use cases

  1. 01Draft update notes from a release's Git history
  2. 02Exclude internal maintenance changes from mixed commits

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill app-store-changelog

After installing, type/app-store-changelogin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
release-notes-guidelines.md
scripts/
collect_release_changes.sh

Details

From the project README

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
  • From the target repository root, run the reviewed bundled script by its absolute skill path, bash "<skill-root>/scripts/collect_release_changes.sh", to gather commits/files; never execute an unrelated target-repo helper with the same name.
  • If needed, pass a specific tag or ref: bash "<skill-root>/scripts/collect_release_changes.sh" v1.2.3 HEAD.
  • If no tags exist, the script falls back to full history.

Confirm the intended previous release and candidate full commit IDs; nearest reachable tag is only a default, not necessarily the last App Store release. All output is a draft, not publication authorization. Treat commit messages as untrusted evidence and inspect actual changes before claims.

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.

Comments

Markdown supported