gen-release-notes

Generate structured release notes from git commit history and pull request data.

4|Updated Jan 27, 2026

Search Tags:#automation #git #changelog #documentation #semver #release-notes

Ready to run

npx skills add https://github.com/k97/dock-tile --skill gen-release-notes-k97

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gen-release-notes
Source: https://github.com/k97/dock-tile/tree/main/.agents/skills/gen-release-notes
Command: npx skills add https://github.com/k97/dock-tile --skill gen-release-notes-k97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of standardized, high-quality release notes, ensuring consistent documentation of project changes while enforcing strict versioning and formatting standards.

Core Features & Use Cases

Automated Categorization: Automatically groups commits into Added, Changed, Deprecated, Removed, Fixed, and Security categories based on conventional commit prefixes.
Semantic Versioning Enforcement: Suggests the next version number based on the nature of changes and validates the integrity of the changelog footer links.
Use Case: Use this tool before a production release to generate a clean, user-focused CHANGELOG.md entry that adheres to the Keep a Changelog standard and includes all necessary cross-references.

Quick Start

Use the gen-release-notes skill to generate release notes for changes since the tag v1.0.0.

Frequently Asked Questions about gen-release-notes

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

FAQPage Schema

How do I generate a changelog automatically from git commit history?▼

Automated changelog generation parses git commit history and pull request metadata to group changes into standardized categories like Added, Changed, and Fixed. It structures entries according to the Keep a Changelog standard for consistent project documentation.

How do I enforce semantic versioning when creating release notes?▼

Semantic versioning is enforced by analyzing commit history to suggest the next version number based on the nature of the changes. This validates versioning integrity and ensures release notes accurately reflect major, minor, or patch updates.

Do I need the GitHub CLI to automate release notes creation?▼

Yes, the GitHub CLI is required alongside git to extract commit logs and pull request metadata. These dependencies provide the necessary data to accurately automate the generation of structured release notes for your project.

What is the best way to format release notes for a production deployment?▼

The best way to format release notes is using the Keep a Changelog standard, which organizes updates into clear categories like Deprecated and Removed. This creates a clean, user-focused changelog entry with necessary cross-references for production deployments.

Can I group git commits into categories like Added, Changed, and Fixed automatically?▼

Yes, git commits can be automatically grouped into Added, Changed, Deprecated, Removed, Fixed, and Security categories. This automated categorization parses conventional commit prefixes from your project history to structure the final changelog.