首页 / 全部技能 / app-store-changelog
A

Skill 详情

app-store-changelog

Generate user-facing App Store release notes from git history since the last tag.

来源平台：GitHub
来源标识：sickn33/antigravity-awesome-skills
源文件：原始说明
编程开发 超热门 GitHub 低 风险 下载 1.91万Stars 3.68万 GitHub Copilot
来源平台GitHub
文档版本SKILL.md
热度超热门
排名信号下载 1.91万
概述 安装 文档 下载

快速判断

Generate user-facing App Store release notes from git history since the last tag.

最后校验2026-05-27
来源平台GitHub
安全提示低
下载副本ZIP 可用

适合任务

  • 把重复任务整理成可复用的 AI 操作流程。
  • 让 AI 在特定场景下按统一规范执行。
  • 为团队或个人工作流提供可复制的任务说明。

输入与输出

输入：任务目标、上下文材料、文件路径、约束条件或需要处理的内容。

输出：按 Skill 说明生成的文档、代码、检查结果、计划、建议或操作步骤。

示例任务

  • 使用 app-store-changelog 帮我处理当前任务，并说明执行前需要确认的输入。
  • 根据 app-store-changelog 的说明，给我一个安全的使用步骤清单。

安装方式

  1. 下载本站提供的 Skill ZIP 并解压。
  2. 把解压后的 Skill 目录放入当前 AI 工具支持的 skills 目录。
  3. 如需在线查看原始内容，可打开 GitHub 的 SKILL.md。

在线原始地址：app-store-changelog/SKILL.md

风险边界

使用前请检查权限、外部依赖和要处理的数据类型。不要把密码、密钥、身份信息或敏感客户资料交给未经确认的 Skill。

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.

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

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

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.
建议反馈