release-notes

Generate structured release notes from git commit history and pull requests.

4|Updated Jul 20, 2026

Search Tags:#automation #git #changelog #documentation #github #release

Ready to run

npx skills add https://github.com/highflame-ai/ai-factory --skill release-notes-highflame-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/release-notes
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill release-notes-highflame-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual archaeology required to summarize software changes, ensuring that release notes are accurate, categorized, and tailored to specific audiences without the risk of accidental publishing.

Core Features & Use Cases

Automated Classification: Automatically buckets changes into breaking changes, features, fixes, and internal updates based on commit conventions.
Multi-Audience Drafting: Generates distinct sections for customers, engineering teams, and executives from a single source of truth.
Use Case: When preparing for a version release, use this skill to generate a comprehensive draft that highlights user-facing features for customers while providing technical migration steps for engineers.

Quick Start

Use the release-notes skill to draft notes for all changes since the last tag for a customer audience.

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 automatically from git commit history?▼

To generate release notes from git commit history, you analyze commit messages and merged pull requests across a specified version range to classify changes into breaking changes, features, fixes, and internal updates.

Can I create different release note drafts for customers, engineers, and executives from a single source?▼

Yes, multi-audience drafting generates distinct documentation sections for customers, engineering teams, and executives simultaneously from a single source of truth derived from your git history.

Do I need GitHub CLI integration to draft multi-audience release notes?▼

Yes, GitHub CLI integration is required alongside git to resolve commit ranges and pull request metadata accurately, ensuring your release notes capture the correct context and categorization.

What is the best way to categorize git commits into breaking changes and features for a changelog?▼

Automated classification buckets git commits into breaking changes, features, fixes, and internal updates based on established commit conventions, eliminating manual archaeology and ensuring accurate changelog categorization.

How does analyzing merged pull requests improve release note generation?▼

Analyzing merged pull requests provides accurate metadata and context for release notes, allowing for precise classification of changes and the creation of audience-specific documentation without accidental publishing risks.

Can I draft release notes for changes between specific version tags?▼

Yes, you can generate structured release notes by analyzing git commit history and merged pull requests across specified version ranges, comparing changes since the last tag to prepare comprehensive drafts.