release-notes

Generates release notes from Git history and CHANGELOG files.

5|2|Updated Mar 20, 2026

Search Tags:#release management #Git #release notes #code documentation #CHANGELOG

Ready to run

npx skills add https://github.com/srnichols/plan-forge --skill release-notes-srnichols

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/srnichols/plan-forge/tree/main/presets/go/.github/skills/release-notes
Command: npx skills add https://github.com/srnichols/plan-forge --skill release-notes-srnichols

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of release notes from Git history and CHANGELOG files, ensuring accurate and efficient documentation of changes for each release.

Core Features & Use Cases

Git History Analysis: Extracts commit information to generate a comprehensive list of changes.
CHANGELOG Integration: Reads and integrates entries from the CHANGELOG.md file for additional context.
Formatting Options: Outputs release notes in formats suitable for GitHub Releases, Slack, or email notifications.
Use Case: Before tagging a release, use this Skill to automatically generate release notes that summarize new features, bug fixes, and breaking changes.

Quick Start

Generate release notes for the latest release using the release-notes skill with the version tag 'v1.2.0'.

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

Automate release notes generation by parsing Git commit messages to extract features, bug fixes, and breaking changes. This process analyzes your commit log and outputs formatted change documentation for each version tag.

What is the best way to integrate CHANGELOG entries into automated release notes?▼

Integrate CHANGELOG entries by reading the CHANGELOG.md file to extract additional context during generation. This combines parsed Git commit history with existing manual entries to produce comprehensive release documentation.

Can I format automated release notes for Slack or GitHub Releases?▼

You can format automated release notes for Slack, GitHub Releases, or email notifications. The formatting options allow you to tailor the generated change summaries for different communication and distribution platforms.

Does this release notes generator work without external dependencies?▼

Yes, the release notes generator works without external dependencies. It relies on internal scripts to parse commit messages and CHANGELOG entries, requiring only an accessible Git repository and a target version tag to execute.

When should I not use automated Git history parsing for release documentation?▼

You should avoid automated Git history parsing for release documentation when your commit messages lack structured conventions or when your project requires manual narrative documentation. The tool depends on consistent commit data to accurately summarize features and fixes.