‹ 首页

release-notes

@phuryn · 收录于 1 周前 · 上游提交 1 周前★ 社区精选

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

场景版本发布更新公告产品更新

适合你，如果你需要把产品改动整理成用户能看懂的发布说明

/ 下载安装
https://github.com/phuryn/pm-skills/tree/main/pm-execution/skills/release-notes ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add phuryn/pm-skills/release-notes
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- phuryn/pm-skills/release-notes
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify phuryn/pm-skills/release-notes
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
23265GitHub stars
~516上下文体积 · 单文件
索引托管

怎么用

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

安装后，Claude 能根据你提供的工单、产品需求文档或变更日志，自动生成面向用户的发布说明。它会按新功能、改进、修复等分类整理，并用通俗语言写出每条变更对用户的好处。

什么时候触发

当你需要写发布说明、更新日志、产品更新公告，或总结已发布的内容时，Claude 会自动触发此技能。

装好后可以这样说
Claude 会读取工单并输出分类后的发布说明。
Claude 会提取变更并转化为面向用户的描述。
技能原文 SKILL.md作者撰写 · MIT · 18468a9
Release Notes Generator

Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.

Context

You are writing release notes for $ARGUMENTS.

If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.

Instructions
  1. Gather raw material: Read all provided tickets, changelogs, or descriptions. Extract:
  2. What changed (feature, improvement, or fix)
  3. Who it affects (which user segment)
  4. Why it matters (the user benefit)
  1. Categorize changes:
  2. New Features: Entirely new capabilities
  3. Improvements: Enhancements to existing features
  4. Bug Fixes: Issues resolved
  5. Breaking Changes: Anything that requires user action (migrations, API changes)
  6. Deprecations: Features being sunset
  1. Write each entry following these principles:
  2. Lead with the user benefit, not the technical change
  3. Use plain language — avoid jargon, internal codenames, or ticket numbers
  4. Keep each entry to 1-3 sentences
  5. Include visuals or screenshots if the user provides them

Example transformations:

  • Technical: "Implemented Redis caching layer for dashboard API endpoints"
  • User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."
  • Technical: "Fixed race condition in concurrent checkout flow"
  • User-facing: "Fixed an issue where some orders could fail during high-traffic periods."
  1. Structure the release notes:

``` # [Product Name] — [Version / Date]

## New Features

  • [Feature name]: [1-2 sentence description of what it does and why it matters]

## Improvements

  • [Area]: [What got better and how it helps]

## Bug Fixes

  • Fixed [issue description in user terms]

## Breaking Changes (if any)

  • Action required: [What users need to do] ```
  1. Adjust tone to match the product's voice — professional for B2B, friendly for consumer, developer-focused for APIs.

Save as a markdown document. If the user wants HTML or another format, convert accordingly.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

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