Agent skill · software engineering · borghei
changelog-generator
Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.
Why this skill is useful
Adds 3 executable scripts for parsing commits, detecting breaking changes, and formatting changelogs that automate release management workflows.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Changelog Generator Generate consistent, auditable changelogs and release notes from Conventional Commits. Parses commit messages, detects semantic version bumps (major/minor/patch), renders Keep a Changelog sections, supports monorepo scoped changelogs, integrates with CI for automated release notes, and enforces commit format with linting. Separates commit parsing, bump logic, and rendering so teams can automate releases without losing editorial control. Keywords changelog, release notes, conventional commits, semantic versioning, semver, Keep a Changelog, commit linting, release automation, monorepo changelog Core Capabilities Commit parsing — parse Conventional Commit messages into structured data (type, scope, description, body, footer); detect breaking changes from ! and BREAKING CHANGE:. Semantic version detection — map commit types to bump levels (breaking→major, feat→minor, others→patch); support pre-release versions. Changelog rendering — Keep a Changelog, GitHub release notes, plain markdown, and JSON output grouped by type. Quality enforcement — commit message linter for CI and pre-commit hooks, strict mode, scope validation, breaking-change documentation requirements. When to Use Before publishing a release tag During CI to generate release notes automatically In PR checks to enforce commit message standards In monorepos where package changelogs need scoped filtering When converting raw git history into user-facing notes As a pre-release checklist step Clarify First Before generating the changelog, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Commit range — since which tag or commit (defines what history is included) [ ] Output format — Keep a Changelog, GitHub release notes, plain markdown, or JSON (sets changelogformatter.py --format) [ ] Version & scope — the release version, and in a monorepo which package scope to filter (sets --version and scoped filtering) Stop rule: ask only the 2-3 that most change the output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/changelog-generator