changelog-generator

Convert git commit history into customer-friendly release notes.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/vZulin/overlay-clock-timer --skill changelog-generator-vzulin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/vZulin/overlay-clock-timer/tree/main/.codex/skills/macos-design/changelog-generator
Command: npx skills add https://github.com/vZulin/overlay-clock-timer --skill changelog-generator-vzulin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts dense git commits into clear, customer-facing release notes, reducing manual writing time and increasing stakeholder understanding.

Core Features & Use Cases

  • Scans Git history to collect changes between versions or time windows.
  • Categorizes changes into features, improvements, bug fixes, breaking changes, and security.
  • Translates technical commits into user-friendly language suitable for public release notes.
  • Formats professional, publication-ready changelog entries ready for docs, stores, or product updates.
  • Supports customization for brand voice and changelog style guidelines.

Quick Start

Run the generator in your git repository to produce a draft changelog for the latest 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 automatically?

To generate release notes from git commit history, the skill scans your repository's commit history, categorizes changes into features or bug fixes, and translates technical jargon into customer-friendly release notes automatically.

Can I customize the changelog format to match my brand voice and style guidelines?

Yes, you can customize the changelog format to match your brand voice and style guidelines. The skill supports customization for professional, publication-ready entries suitable for docs, stores, or product updates.

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

The best way to translate technical git commits into user-facing release notes is to use an automated generator that categorizes changes and formats structured changelog entries into user-friendly language suitable for public updates.

Does the changelog generator categorize git commits into features, improvements, and bug fixes?

Yes, the changelog generator categorizes git commits into features, improvements, bug fixes, breaking changes, and security updates. It scans history between versions or time windows to structure these categories.

How do I collect changes between versions for a software release changelog?

To collect changes between versions for a software release changelog, run the generator in your git repository. It scans the git history within a specified time window or version range to produce a draft changelog.

Are publication-ready changelog entries generated automatically from git history?

Yes, publication-ready changelog entries are generated automatically from git history. The skill formats professional release notes that can be directly published to documentation, app stores, or product update channels.