releasenotes

Generate categorized Markdown changelogs from git history since the latest release tag.

134|67|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/OpenHands/skills --skill releasenotes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasenotes
Source: https://github.com/OpenHands/skills/tree/main/skills/releasenotes
Command: npx skills add https://github.com/OpenHands/skills --skill releasenotes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of release notes by collecting changes from the git history since the last release tag, saving time and ensuring consistency.

Core Features & Use Cases

  • Generate categorized changelogs (Breaking Changes, Added, Changed, Fixed, Notes) from git history.
  • Include PR links and contributor attribution, aligned with release styles.
  • Use for preparing GitHub releases and internal changelogs across multiple projects.

Quick Start

Run the releasenotes skill against your repository to generate a release-note block for the latest tag.

Frequently Asked Questions about releasenotes

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

FAQPage Schema
How do I generate a changelog from git history for a new release?

To generate a changelog from git history, the Skill collects commits since the most recent release tag and categorizes them into structured sections like Added, Changed, and Fixed. It outputs a ready-to-paste Markdown block for your release notes.

Can I automatically include PR links and contributor attribution in my release notes?

Yes, you can automatically include PR links and contributor attribution in release notes. The Skill parses git history to align with standard release styles, appending the corresponding pull request URLs and crediting the contributors directly in the output.

What is the best way to categorize breaking changes in a semantic versioning changelog?

The best way to categorize breaking changes in a semantic versioning changelog is to isolate them in a dedicated section. The Skill automatically scans git history and separates breaking changes from standard updates to ensure they are clearly highlighted.

Do I need semantic versioning tags to generate release notes?

Yes, you need semantic versioning tags to generate release notes effectively. The Skill uses the most recent release tag as a baseline to collect subsequent git history, ensuring only the changes since the last release are included.

How do I prepare a ready-to-publish markdown block for a GitHub release?

To prepare a ready-to-publish markdown block for a GitHub release, run the Skill against your repository. It processes the git history and outputs formatted markdown with categories, notes, and PR links ready for publication.