draft-release-notes

Draft user-facing release notes from git commit history since a tag boundary.

411|21|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/luxury-yacht/app --skill draft-release-notes-luxury-yacht
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-release-notes
Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/draft-release-notes
Command: npx skills add https://github.com/luxury-yacht/app --skill draft-release-notes-luxury-yacht

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It saves maintainers from manually writing inconsistent, time-consuming release notes by automatically summarizing changes from git history since the last tag.

Core Features & Use Cases

  • Change-range release notes generation — generates notes for the latest tag to HEAD, a custom from-tag to HEAD range, or a from-tag to to-tag range, based on your git tag selection.
  • Keep a Changelog–style categorization — groups commit-derived changes under user-facing sections like Added, Changed, Fixed, Security, Deprecated, and Removed only when entries exist.
  • User-focused formatting rules — produces release notes that describe what users can do or see, while omitting PR numbers, commit hashes, and build-only/merge/version-bump noise.

Quick Start

Ask your AI assistant to run /draft-release-notes to generate user-ready release notes from the most recent tag through the current HEAD.

Frequently Asked Questions about draft-release-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes automatically from git commit history?

Generate release notes automatically by extracting and summarizing git commit history since a specified tag boundary. The tool filters out merges and build-only changes to produce clean, user-facing summaries.

Can I create changelog entries for a specific range between two git tags?

Yes, you can create changelog entries for a custom range by specifying a from-tag to to-tag span. It also supports generating notes from a specific tag to HEAD or from the latest tag to HEAD.

How do I format git commits into Keep a Changelog categories like Added and Fixed?

Format git commits into Keep a Changelog categories by grouping commit-derived changes under user-facing sections. It includes Added, Changed, Fixed, Security, Deprecated, and Removed sections only when entries exist.

Does release note generation exclude commit hashes and PR numbers for user readability?

Yes, release note generation omits PR numbers and commit hashes to improve user readability. It produces notes describing what users can see or do while filtering out version-bump noise.

What is the best way to draft user-facing release notes without manual formatting?

Draft user-facing release notes without manual formatting by using an automated summarizer that processes git history. It applies Keep a Changelog conventions and formats output with a version date header.

Can I filter out merge commits and build-only changes when summarizing git history?

Yes, you can filter out merge commits and build-only changes when summarizing git history. The tool automatically excludes this noise to ensure the final release notes focus only on user-facing modifications.