release-notes

原文涵盖的主题

• Release Notes Generator
• Context
• Instructions

Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes. 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. 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

这里只展示节选，请以完整原文和当前要求为准。