release-notes

Generate Markdown release notes from git tags and GitHub pull requests.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill release-notes-thanhhuong0209
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/Thanhhuong0209/DLT-Normalization/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/Thanhhuong0209/DLT-Normalization --skill release-notes-thanhhuong0209

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of release notes by analyzing git commit history and GitHub pull requests, saving developers significant manual effort and ensuring consistent documentation.

Core Features & Use Cases

  • Automated Tag Analysis: Identifies commits and PRs between specified git tags.
  • PR Metadata Fetching: Gathers titles, labels, bodies, and author information for each PR.
  • Categorization: Classifies PRs into Breaking Changes, Highlights, Core Library, Docs, and Chores.
  • New Contributor Identification: Detects first-time contributors based on their merged PRs.
  • Formatted Output: Generates release notes in a structured Markdown format.

Quick Start

Generate release notes for the tag 'v1.2.0' and compare it with the previous tag.

Frequently Asked Questions about release-notes

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

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

Generate release notes from git tags automatically by analyzing commit history and GitHub pull requests to summarize changes, categorize contributions, and identify new contributors in a structured Markdown document.

Can I categorize GitHub pull requests into sections for a changelog?

Categorize GitHub pull requests into sections for a changelog by fetching PR metadata and classifying entries into Breaking Changes, Highlights, Core Library, Docs, and Chores for structured formatting.

Do I need the gh tool to generate release notes from GitHub PRs?

You need the gh tool installed to generate release notes from GitHub PRs, as it fetches pull request metadata like titles, labels, bodies, and author information required for the analysis.

How does detecting first-time contributors in release notes work?

Detecting first-time contributors in release notes works by analyzing merged GitHub pull requests within a git tag range and identifying authors who have not previously contributed to the project.

What is the best way to compare commits between two git tags for release documentation?

The best way to compare commits between two git tags for release documentation is to parse the commit history and fetch GitHub PR metadata to summarize categorized changes and new contributors.

Are there limitations when using git tags to generate structured Markdown release notes?

Limitations when using git tags to generate structured Markdown release notes include relying on consistent PR labeling for accurate categorization and requiring the gh tool for fetching all pull request metadata.