Agent skill · software engineering · alirezarezvani
changelog-generator
Write release notes and CHANGELOG.md from commits and pick the next semver version. Use whenever the user is cutting a release, asks what changed since the last one or what version comes next, or wants commits linted first.
Why this skill is useful
Adds executable scripts for generating changelogs and validating commit messages that automate release management processes.
What it needs
Requires python3 installed locally. About 4k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Changelog Generator Tier: POWERFUL Category: Engineering Domain: Release Management / Documentation Overview Use this skill to produce consistent, auditable release notes from Conventional Commits. It separates commit parsing, semantic bump logic, and changelog rendering so teams can automate releases without losing editorial control. Core Capabilities Parse commit messages using Conventional Commit rules Detect semantic bump (major, minor, patch) from commit stream Render Keep a Changelog sections (Added, Changed, Fixed, etc.) Generate release entries from git ranges or provided commit input Enforce commit format with a dedicated linter script Support CI integration via machine-readable JSON output When to Use Before publishing a release tag During CI to generate release notes automatically During PR checks to block invalid commit message formats In monorepos where package changelogs require scoped filtering When converting raw git history into user-facing notes Key Workflows 1. Generate Changelog Entry From Git 2. Generate Entry From stdin/File Input 3. Update CHANGELOG.md 4. Compute the Next Version From Commits When the user has not decided the next version, derive it instead of guessing: Output JSON contains recommendedversion, bumptype (major/minor/patch/none), and with --include-commands the exact git tag commands. Feed recommendedversion into generatechangelog.py --next-version. Pre-releases: add --prerelease alpha beta rc. Input must be real git log --oneline output (hex hashes); a sample lives at assets/samplegitlog.txt. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/changelog-generator--3915a4