Menu

Individual skill

changelog-generator

0upvotes

Converts commits or development updates into clean, categorized release notes and changelogs. Use when preparing a release and raw commit history needs to become human-readable notes.

skills/documentation/changelog-generator/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Turn a raw list of commits, PR titles, or dev notes into a clean, categorized changelog entry that a user (not just an engineer) can read and understand what changed.

## When to Use

- Preparing release notes for a new version.
- A commit history is a mix of styles/quality and needs to become one coherent changelog.
- The user pastes a list of merged PRs or commit messages and wants them turned into notes.

## What to Analyze / Do

1. **Categorize each change** — typically: Added, Changed, Fixed, Removed, Deprecated, Security (following a Keep a Changelog–style structure, or the project's existing convention if different).
2. **Rewrite for the reader, not the author** — "fix null check in auth.js" becomes "Fixed an issue where login could fail unexpectedly for some users." Focus on user-visible impact, not implementation detail, unless the audience is technical (e.g. a library's changelog for other engineers, where technical specificity is appropriate).