skills.rest
landmaster135
landmaster135COMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog-generator

Aggregate git commits into CHANGELOG.md release notes with grouped sections.

Updated Apr 9, 2025
Search Tags:#automation#changelog#versioning#release-notes#git-log#commit-grouping
One-click install
npx skills add https://github.com/landmaster135/devbox --skill changelog-generator-landmaster135
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/landmaster135/devbox/tree/main/.config/codex/skills/project-documentation/commands/changelog-generator-personal
Command: npx skills add https://github.com/landmaster135/devbox --skill changelog-generator-landmaster135

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams automatically generate CHANGELOG-style release notes by aggregating commits within a specified time window and formatting them for human readers.

Core Features & Use Cases

  • Group commits into user-facing sections (Features, Improvements, Refactor, Bug Fixes, Documentation) to mirror typical changelogs.
  • Produce a CHANGELOG.md-compatible entry with a top-level version/date line and PR references when available.
  • Interactively prompt for the exact start datetime and optional end/constraints, then generate a structured, readable release notes draft for distribution.

Quick Start

Specify the exact start datetime when prompted, and the tool will compile a CHANGELOG-style release notes from commits since that date.

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

To generate release notes from git commits automatically, this skill aggregates commit messages within a specified time window, groups them into conventional changelog sections like Features and Bug Fixes, and outputs a formatted entry for your CHANGELOG.md file.

How are git log messages grouped for a changelog?▼

Git log messages are grouped for a changelog by categorizing commits into standard user-facing sections such as Improvements, Refactor, and Documentation, ensuring the final release notes are structured and human-readable.

Can I filter commits by version or PR when generating release notes?▼

Yes, you can filter commits by version or PR when generating release notes by applying optional constraints like an end date, target version, or PR filters alongside the required start datetime prompt.

What is the best way to format commit history for a CHANGELOG.md file?▼

The best way to format commit history for a CHANGELOG.md file is to compile commits from a specific time window into a structured entry featuring a top-level version and date line, augmented with PR references where available.

Do I need to specify a start date to compile a changelog draft?▼

Yes, you need to specify an exact start datetime because the tool interactively prompts for this boundary to accurately aggregate and compile your release notes draft from that specific point forward.

Related Skills

Explore More Software Engineering Skills→
reomgitreomgit

gstack-openclaw-retro

Analyze git commit history and code quality metrics for weekly engineering retrospectives.

Community
Advanced
deepklaritydeepklarity
87

dk-changelog

Generate changelog entries from git changes and prepend them to CHANGELOG.md.

Official
Intermediate
ZeiZelZeiZel
2

changelog

Generate CHANGELOG.md from Git history with Keep a Changelog format.

Community
Advanced
fghaffarfghaffar

retro

Generate weekly engineering retrospective reports from Git commit history and metrics.

Community
Advanced