release-notes

Generate markdown release notes from Git commits and pull requests.

Updated Dec 3, 2025

Search Tags:#automation #changelog #versioning #github #release notes #git tagging

Ready to run

npx skills add https://github.com/azeemigi/advent-2025 --skill release-notes-azeemigi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/azeemigi/advent-2025/tree/main/.github/skills/.claude/skills/release-notes
Command: npx skills add https://github.com/azeemigi/advent-2025 --skill release-notes-azeemigi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of creating comprehensive release notes, tagging code repositories, and publishing new versions, saving significant developer time and ensuring consistency.

Core Features & Use Cases

Automated Change Gathering: Collects commits, PRs, and issues between releases.
Structured Note Generation: Writes release notes in a predefined Markdown format.
Repository Tagging & Pushing: Creates and pushes Git tags for new versions.
Use Case: After merging a new feature branch, use this Skill to generate the release notes for the upcoming v1.2.0 release, automatically tagging the commit and pushing the tag to GitHub.

Quick Start

Use the release-notes skill to create release notes for version v1.0.16.

Frequently Asked Questions about release-notes

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

FAQPage Schema

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

Automated release notes generation analyzes Git commit history and pull requests to categorize changes into features, bug fixes, and breaking changes. It compiles these categorized changes into a structured markdown file for your new software version.

Can I automatically create and push git tags when generating a changelog?▼

Yes, changelog generation can be combined with Git tagging. After creating the markdown release notes file, the process creates a Git tag for the new version and pushes it directly to your GitHub repository.

How do I structure release notes into features, bug fixes, and breaking changes?▼

Structuring release notes involves parsing Git commit history and pull requests to identify change types. The system categorizes commits into features, bug fixes, and breaking changes, then writes them into a predefined Markdown format.

Do I need to specify a base version before generating release notes?▼

Yes, you must confirm a base version to diff against. The release notes generation requires user confirmation for the base version so it can accurately collect commits, PRs, and issues between that release and the current state.

What is the best way to automate versioning and release notes for GitHub repositories?▼

Automating versioning and release notes involves analyzing Git history to categorize changes, generating a Markdown changelog, and pushing a Git tag to GitHub. This streamlines publishing new versions and ensures consistency across releases.