‹ 首页

app-store-changelog

@dimillian · 收录于 1 周前 · 上游提交 4 个月前

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.

场景发布前准备版本更新

适合你，如果每次发版都要手动整理用户可见的变更记录

/ 下载安装
https://github.com/dimillian/skills/tree/main/app-store-changelog ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add dimillian/skills/app-store-changelog
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- dimillian/skills/app-store-changelog
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify dimillian/skills/app-store-changelog
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
3846GitHub stars
~639最小装载
~1.2K含声明引用
~1.2K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 05ba982 · 表述以原文为准
它做什么

安装后，Claude 能根据 Git 提交记录，自动生成面向用户的 App Store 更新说明。它会筛选出对用户有影响的改动，按“新功能”“改进”“修复”分类，并写成简洁的要点列表。

什么时候触发

当你要求生成 App Store 更新日志、发布说明或“What's New”文本时触发。需要项目有 Git 标签或指定版本范围。

装好后可以这样说
Claude 会运行脚本收集提交并生成要点。
指定标签范围，Claude 会使用该范围。
Claude 会筛选用户可见的改动并分类。
技能原文 SKILL.md作者撰写 · MIT · 05ba982

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.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…