Release Notes & Changelog Writer

Commit messages are written for the people making the change, not the people using it. Turning them into release notes means sorting out chores and CI noise, spotting breaking changes, and rewriting everything in plain words.

This skill gives your AI a procedure for that. It exports the right git history for your merge style (or a merged pull request list from the GitHub CLI), groups the changes into Added, Changed, Deprecated, Removed, Fixed and Security, drops internal noise while listing it for a quick check, pairs reverts with the commits they undo, and moves anything that mentions a CVE or advisory into Security. Breaking changes get who is affected, what to do and a before/after example. It suggests major, minor or patch, and writes both user-facing release notes and a Keep a Changelog entry.

Inside: SKILL.md, a classification reference (export commands, grouping rules, semver rules), a writing guide with before/after rewrites and a final checklist, two templates, and a Node helper with no dependencies that parses git log output or PR JSON using Conventional Commits with keyword fallbacks. Examples include a 27-commit sample log, the script's output and the finished notes.

For maintainers of apps, libraries, CLIs and services. It reads messages and PR titles, not code, so vague commits are flagged for review rather than guessed. It never tags, pushes or publishes on its own.