release-notes-and-changelog

Generates formatted release notes and changelogs from git commit history.

Updated Aug 23, 2026

Search Tags:#automation #changelog #documentation #conventional commits #release notes #git history

Ready to run

npx skills add https://github.com/EtroxTaran/conductor --skill release-notes-and-changelog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes-and-changelog
Source: https://github.com/EtroxTaran/conductor/tree/main/.claude/skills/release-notes-and-changelog
Command: npx skills add https://github.com/EtroxTaran/conductor --skill release-notes-and-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of user-facing release notes and changelogs by parsing git commit history, saving significant manual documentation effort.

Core Features & Use Cases

Automated Changelog Generation: Creates structured release notes based on commit messages.
Categorization: Groups changes into Features, Fixes, and Performance improvements.
Use Case: After a development sprint, use this Skill to automatically generate the CHANGELOG.md file for the new release, ensuring accurate and consistent documentation.

Quick Start

Generate release notes from the git history since the last tag.

Frequently Asked Questions about release-notes-and-changelog

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

FAQPage Schema

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

To generate release notes from git history automatically, this Skill parses your commit log, filters for conventional commit types like feat, fix, and perf, and formats them into a structured markdown changelog file.

What are conventional commits and how do they work with changelog generation?▼

Conventional commits use standardized prefixes like feat, fix, and perf to categorize code changes. This Skill uses these commit types to automatically group git history entries into structured Features, Fixes, and Performance sections in your release notes.

Can I use this to create a markdown changelog from my commit messages?▼

Yes, you can create a markdown changelog from your commit messages. The Skill processes your git history and outputs a structured markdown file that categorizes changes by type and explicitly handles breaking changes.

What is the best way to document breaking changes in release notes?▼

The best way to document breaking changes in release notes is to parse git history for specific conventional commit flags. This Skill identifies breaking changes and ensures they are distinctly formatted within the generated markdown changelog.

Does this changelog generator work with any git repository format?▼

This changelog generator works with any git repository utilizing conventional commit messages. It filters commits based on types like feat, fix, and perf, requiring your git history to follow this naming convention for accurate categorization.

Why are some commits missing from my generated changelog?▼

Commits may be missing from your generated changelog if they do not follow conventional commit formatting. The Skill specifically filters git history for recognized types like feat, fix, and perf, omitting non-standard commit messages.