skills.rest
JayJihyunKim
JayJihyunKimCOMMUNITY
Explore all skills by this author →
GitHub

changelog-writer

Generate versioned CHANGELOG.md files from git history and trail decisions.

1|Updated Apr 16, 2026
Search Tags:#automation#git#changelog#versioning#software-engineering#release-notes#decision-trail
One-click install
npx skills add https://github.com/JayJihyunKim/rein --skill changelog-writer-jayjihyunkim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-writer
Source: https://github.com/JayJihyunKim/rein/tree/main/plugins/rein-core/skills/changelog-writer
Command: npx skills add https://github.com/JayJihyunKim/rein --skill changelog-writer-jayjihyunkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a standardized CHANGELOG.md by extracting and classifying git history and trail decisions, reducing manual release documentation.

Core Features & Use Cases

  • Collects git history over a specified range (previousTag..HEAD).
  • Classifies changes into Added, Fixed, Changed, and Breaking Changes.
  • Produces a versioned CHANGELOG.md with sections for each category and a breaking changes note.
  • Provides a report that can be merged into README version history.

Quick Start

Run the changelog-writer on the target repository to convert the latest git changes into a structured CHANGELOG.md.

Frequently Asked Questions about changelog-writer

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

FAQPage Schema
How do I automate CHANGELOG generation from git history?▼

You can automate CHANGELOG generation by processing a specified commit range (previousTag..HEAD) to extract commit messages and classify them into structured sections like Added, Fixed, Changed, and Breaking Changes.

What is the best way to categorize git commits for release notes?▼

The best way to categorize git commits for release notes is to apply classification rules mapping feat, fix, refactor, and BREAKING CHANGE tags directly from your git history into distinct changelog sections.

Can I cross-check README version history updates with my new changelog?▼

Yes, you can cross-check README version history updates with your new changelog. The generated report provides a versioned summary that can be directly merged into your README to ensure version consistency.

How do I generate a changelog for a specific range of previous tags?▼

To generate a changelog for a specific range of previous tags, specify the commit range as previousTag..HEAD, allowing the tool to collect git history and trail decisions exclusively within that release boundary.

Does changelog generation work without manual release documentation?▼

Yes, changelog generation works without manual release documentation by automatically extracting and classifying git history and trail decisions, which reduces the need to manually write release notes for software projects.

Related Skills

Explore More Software Engineering Skills→
mikkeymoomikkeymoo
1

mm-changelog

Generate a Keep a Changelog changelog from conventional Git commits.

Community
Intermediate
optaveoptave
86

release

Generate release notes and PR scaffolding from commit history.

Official
Advanced
ValorVieValorVie
5

release-standards

Enforce semantic versioning and Keep a Changelog formatting for software releases.

Community
Advanced
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate