Index of every page on this site: llms.txt
All skills
dimillian avatar

/app-store-changelog

@05ba982 official
by Thomas Ricouarddimillian/skills4k stars
208
Run it yourself

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.

  • 4 files
  • 5.5 KB
  • Updated 9 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/dimillian/skills/app-store-changelog

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈76 tokens for metadata: the name and description. ≈660 when used: this file. ≈467 more on demand in 2 files.

Description uses 3.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈304 characters, or 3.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 05ba982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 9 months ago
  • Git/VCS
  • changelog
  • release-notes
  • app-store
  • ios
  • versioning
  • commit-history

README badge

README badge for dimillian/skills/app-store-changelog

Generates user-facing App Store release notes by extracting commits since the last git tag and filtering for user-visible changes. Groups changes by theme (New, Improved, Fixed) and translates them into clear, benefit-focused bullets suitable for storefront submission.

Generated from the current SKILL.md.

Does this skill work with monorepos or multi-target apps?
The skill collects all commits in the specified git range and touched files. You can filter the output manually or pass specific refs to `collect_release_changes.sh`, but the skill does not have built-in filtering for monorepo paths or per-target changelogs.
What if the repo has no git tags?
The `collect_release_changes.sh` script falls back to full git history if no tags exist. You can also specify a custom ref or tag range to narrow the scope.
Does this generate changelogs for internal release notes or only App Store?
The skill is designed for user-facing App Store release notes. It filters out internal-only changes (build scripts, refactors, CI), but you can adapt the output format for other storefront or internal documentation needs.
How does the skill decide what counts as user-impacting?
The skill scans commit messages and touched files to identify user-visible changes, then groups them by theme (New, Improved, Fixed) and drops commits marked as chore, refactor, or CI. Ambiguous changes are flagged for manual clarification.

Generated from the current SKILL.md. These answers refresh after source changes.