changelog-generator

Generate user-facing changelogs from git commit history with categories and formatting.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/WesleyMarinho/codeseek-marketplace --skill changelog-generator-wesleymarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/WesleyMarinho/codeseek-marketplace/tree/main/skills/changelog-generator
Command: npx skills add https://github.com/WesleyMarinho/codeseek-marketplace --skill changelog-generator-wesleymarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of user-facing changelogs by analyzing git commit history, transforming technical details into clear, customer-friendly release notes.

Core Features & Use Cases

  • Scans Git History: Analyzes commits within specified date ranges or between versions.
  • Categorizes Changes: Groups commits into features, improvements, bug fixes, etc.
  • Translates Technical to User-Friendly: Converts developer-focused commits into easily understandable language.
  • Use Case: Automatically generate release notes for your next software update by analyzing all commits made since the last release.

Quick Start

Create a changelog from commits since the last release.

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, this Skill scans your git commit history within a specified date range or between version tags, categorizing technical changes into customer-friendly release notes automatically.

Can I create a changelog between two specific version tags?

Yes, you can create a changelog between version tags. The Skill analyzes commit history within specified time periods or between version tags to group commits into features, improvements, and bug fixes.

How does converting technical commits into user-friendly changelogs work?

Converting technical commits into user-friendly changelogs works by filtering out noise from your git history and transforming developer-focused messages into clear language that customers can easily understand.

Does the changelog generator require any external dependencies or APIs?

No external dependencies or APIs are required. The Skill operates independently by analyzing your git commit history and applying custom formatting guidelines to produce the final changelog output.

What's the best way to categorize git commits for software release notes?

The best way to categorize git commits for release notes is using a tool that automatically groups commit history into standard categories like features, improvements, and bug fixes before transforming them into readable text.

Can I apply custom formatting guidelines to my generated changelog?

Yes, you can apply custom formatting guidelines. The Skill supports custom formatting to ensure the generated changelog matches your specific release notes structure and presentation style.