changelog-generator

Generate user-facing release notes from Git commit history.

115|6|Updated Dec 28, 2025

Search Tags:#automation #git #changelog #release-notes #commit-history

Ready to run

npx skills add https://github.com/jewbetcha/opentrace --skill changelog-generator-jewbetcha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/jewbetcha/opentrace/tree/main/.agents/skills/changelog-generator
Command: npx skills add https://github.com/jewbetcha/opentrace --skill changelog-generator-jewbetcha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of user-facing release notes from git commit history.

Core Features & Use Cases

Scan Git History: Analyzes commits from a specific time period or between versions
Categorizes Changes: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)
Translates Technical → User-Friendly: Converts developer commits into customer language
Formats Professionally: Creates clean, structured changelog entries
Filters Noise: Excludes internal commits (refactoring, tests, etc.)
Follows Best Practices: Applies changelog guidelines and your brand voice

Quick Start

From your project repository: Generate a changelog from commits since last release Generate a changelog for commits from the past week Create release notes for version 2.5.0

Frequently Asked Questions about changelog-generator

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

FAQPage Schema

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

To generate release notes from git commit history, analyze commits between versions or time periods, categorize changes into logical groups, and format the output into polished changelog entries suitable for public documentation.

Can I automatically categorize git commits into features and bug fixes for a changelog?▼

Yes, you can automatically categorize git commits for a changelog by grouping commit history into logical categories such as features, improvements, bug fixes, breaking changes, and security updates.

What is the best way to translate technical git commits into user-friendly release notes?▼

The best way to translate technical git commits into user-friendly release notes is to convert developer commit messages into customer language while filtering out internal noise like refactoring or tests.

How do I filter internal commits like refactoring from my changelog?▼

You can filter internal commits like refactoring from your changelog by applying a generation process that excludes internal noise and only translates user-facing changes into the final release notes.

Does automated changelog generation work for weekly sprint updates?▼

Yes, automated changelog generation works for weekly sprint updates by scanning git history from a specific time period or between versions to create structured release notes for that timeframe.