---
name: Release Notes
slug: release-notes-2
category: Writing
description: Release Notes generates user-facing release notes from the change history since the last release. Use it when asked to produce release notes or when the /release-notes command runs.
github: "https://github.com/ccch1mneyyy/dsh-TUI/tree/main/skills/release-notes"
language: TypeScript
stars: 1889
forks: 79
install: "npx degit https://github.com/ccch1mneyyy/dsh-TUI/tree/main/skills/release-notes ~/.claude/skills/release-notes"
installs_to: ~/.claude/skills/release-notes
source_path: skills/release-notes/SKILL.md
collection_size: 7
category_size: 1012
collection_url: "https://dirskills.com/collections/ccch1mneyyy/dsh-TUI"
added: 2026-08-18T06:59:33.149Z
last_synced: 2026-08-18T06:59:33.149Z
canonical_url: "https://dirskills.com/skills/release-notes-2"
---

# Release Notes

Release Notes generates user-facing release notes from the change history since the last release. Use it when asked to produce release notes or when the /release-notes command runs.

**Install:**

```bash
npx degit https://github.com/ccch1mneyyy/dsh-TUI/tree/main/skills/release-notes ~/.claude/skills/release-notes
```

## README

# Release Notes

Generate user-facing release notes for the current project since the last release.

## Procedure

1. Determine the last release point (git tags) and collect the change set since then (git log / diff of user-facing surfaces).
2. Classify changes:
   - **新功能** (new features)
   - **改进** (improvements / behavior changes)
   - **修复** (bug fixes)
   - **破坏性变更** (breaking changes — call these out first)
   - **内部** (chore/refactor — omit from user-facing notes or fold into a footnote)
3. Write notes in the user's language, focused on what changed for users — not implementation details.
4. Reference issues/PRs where known, keep each bullet one line, group under the sections above.

## Constraints

- Do not fabricate changes — only what the history shows.
- Breaking changes must be listed first, with migration hints.