Agent Skills › AFK-surf/OpenBridge › app-store-changelog

app-store-changelog

GitHub

基于Git历史生成面向用户的App Store更新日志。通过脚本收集变更，筛选用户可见影响，去重并分类为新增、改进和修复，最终撰写简洁明了的发布说明。

.agents/skills/app-store-changelog/SKILL.md AFK-surf/OpenBridge

Trigger Scenarios

生成App Store更新日志根据Git标签或提交记录编写版本说明创建面向用户的发布备注

Install

npx skills add AFK-surf/OpenBridge --skill app-store-changelog -g -y

More Options

Non-standard path

npx skills add https://github.com/AFK-surf/OpenBridge/tree/main/.agents/skills/app-store-changelog -g -y

Use without installing

npx skills use AFK-surf/OpenBridge@app-store-changelog

指定 Agent (Claude Code)

npx skills add AFK-surf/OpenBridge --skill app-store-changelog -a claude-code -g -y

安装 repo 全部 skill

npx skills add AFK-surf/OpenBridge --all -g -y

预览 repo 内 skill

npx skills add AFK-surf/OpenBridge --list

SKILL.md

Frontmatter

{
    "name": "app-store-changelog",
    "description": "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."
}

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.

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.