release-notes · 把本次变更写成用户读得懂的发布说明

作者提供的示例，实际效果取决于你的输入和使用工具。

输入

编辑虚构材料：纸舟工作台v2.3，2026-09-01已全量。A：导出支持选择日期；B：修复空文件夹误显示加载失败；C：10月1日起CSV时间字段改ISO 8601，导入方需更新解析。无性能测量。

输出

编辑示例 · 未运行

纸舟工作台 v2.3｜2026-09-01

新功能

导出时可以选择起止日期，只下载这段时间内的记录。

修复

空文件夹现在显示空状态，不再误提示“加载失败”。

需要管理员处理

从10月1日起，CSV导出中的时间字段将采用ISO 8601格式。若你用脚本导入CSV，请在此之前更新日期解析规则，并用导出样本核对时区。

以上功能已全量开放；日期格式迁移尚未生效，生效日为10月1日。

---
name: release-notes
description: "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."
---

## 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:
   - What changed (feature, improvement, or fix)
   - Who it affects (which user segment)
   - Why it matters (the user benefit)

2. **Categorize changes**:
   - **New Features**: Entirely new capabilities
   - **Improvements**: Enhancements to existing features
   - **Bug Fixes**: Issues resolved
   - **Breaking Changes**: Anything that requires user action (migrations, API changes)
   - **Deprecations**: Features being sunset

3. **Write each entry** following these principles:
   - Lead with the user benefit, not the technical change
   - Use plain language — avoid jargon, internal codenames, or ticket numbers
   - Keep each entry to 1-3 sentences
   - 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."

4. **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]
   ```

5. **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.

先看看示例

输入

输出

纸舟工作台 v2.3｜2026-09-01

新功能

修复

需要管理员处理

方法说明