changelog-generator

Generate structured changelogs from git history using conventional commit parsing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/olli107x/claude-code-starter-kit --skill changelog-generator-olli107x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/olli107x/claude-code-starter-kit/tree/main/skills/development/git/changelog-generator
Command: npx skills add https://github.com/olli107x/claude-code-starter-kit --skill changelog-generator-olli107x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of CHANGELOG.md files by parsing git commit history, transforming technical commits into user-friendly release notes.

Core Features & Use Cases

  • Automated Changelog Generation: Creates structured release notes based on git logs.
  • Conventional Commit Parsing: Understands and categorizes commits (feat, fix, refactor, etc.).
  • Smart Grouping: Organizes changes by scope (e.g., products, auth) and type.
  • Use Case: Before releasing a new version, use this Skill to quickly generate accurate and well-formatted release notes for your users and stakeholders.

Quick Start

Use the changelog-generator skill to generate release notes for commits since the last tag.

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

Generate release notes from git history automatically by parsing conventional commits and categorizing changes into features, bug fixes, performance improvements, and breaking changes. This creates structured, user-friendly changelogs without manual writing.

Does the changelog generator work with conventional commit formats like feat and fix?▼

Yes, the changelog generator works with conventional commit formats by parsing commit types like feat, fix, and refactor. It understands these conventional commit prefixes to accurately categorize git changes into appropriate release note sections.

Can I generate a changelog for a specific date range or version tag?▼

Yes, you can generate a changelog for a specific date range or version tag. The generator supports filtering git history by date ranges and version tags to produce structured release notes scoped to your desired release boundaries.

How to group git commits by scope when creating release documentation?▼

Group git commits by scope when creating release documentation by parsing commit scopes to organize changes by project area, such as products or auth, alongside their commit type for clear, structured release documentation.

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

The best way to turn technical git commits into user-friendly release notes is using automated conventional commit parsing with smart categorization. This transforms raw git logs into structured documentation grouped by features, fixes, and breaking changes.

Do I need to follow strict conventional commits to generate a changelog?▼

You need to follow conventional commit standards like feat, fix, and refactor prefixes for the changelog generator to accurately parse and categorize your git history into structured, user-friendly release notes.