skills.rest
julianromli
julianromliCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog-generator

Analyze git commit history to generate structured customer-facing release notes.

141|20|Updated Dec 19, 2025
Search Tags:#automation#git#changelog#markdown#categorization#release-notes
One-click install
npx skills add https://github.com/julianromli/opencode-template --skill changelog-generator-julianromli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/julianromli/opencode-template/tree/main/skill/changelog-generator
Command: npx skills add https://github.com/julianromli/opencode-template --skill changelog-generator-julianromli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts technical git commits into clear, customer-facing release notes, eliminating hours of manual drafting.

Core Features & Use Cases

  • Scans Git History: Analyzes commits to identify changes across versions and time frames.
  • Categorizes Changes: Groups commits into features, improvements, fixes, breaking changes, and security events.
  • Translates Technical → Customer-Friendly: Converts developer language into user-friendly summaries.
  • Formats Professionally: Produces clean, structured markdown changelogs ready for release notes.
  • Filters Noise: Excludes internal commits like refactors and tests.
  • Reviews & Branding: Aligns output with your branding guidelines and release notes style.

Quick Start

Run the changelog generator from your repository root to produce the latest release notes.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I generate customer-friendly release notes from git commit history?▼

To generate customer-friendly release notes from git commit history, you can analyze your repository's commits to categorize changes into features, fixes, and breaking changes, then translate them into structured markdown changelogs.

Can I filter out internal commits like refactors and tests from my changelog?▼

Yes, you can filter out internal commits like refactors and tests from your changelog. The generation process excludes noisy internal commits and focuses on categorizing meaningful changes for customer-facing release notes.

How do I categorize git commits into features, fixes, and breaking changes for a markdown changelog?▼

To categorize git commits into features, fixes, and breaking changes for a markdown changelog, you can apply user-defined categorization rules that group commits into distinct technical and security events.

Does this changelog generator support analyzing commits between specific date ranges or versions?▼

Yes, this changelog generator supports analyzing commits between specific date ranges or versions. It performs deterministic extraction from git history within scoped analysis parameters to produce targeted release notes.

What is the best way to turn technical git commits into structured markdown release notes?▼

The best way to turn technical git commits into structured markdown release notes is to use deterministic extraction to translate developer language into user-friendly summaries while aligning the output with your branding guidelines.

Related Skills

Explore More Product & Management Skills→
AirMileAirMile

core-changelog

Generate user-facing changelogs from conventional git commit history.

Community
Advanced
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
QredenceQredence
108

changelog-generator

Convert git commits into customer-facing release notes.

Official
Intermediate