skills.rest
Arete-Consortium
Arete-ConsortiumOFFICIAL
Explore all skills by this author →
GitHub

changelog

Generate Keep a Changelog formatted release notes from conventional git commits.

4|2|Updated Jan 27, 2026
Search Tags:#git#changelog#markdown#conventional commits#release notes#semantic versioning#keep a changelog
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill changelog-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/personas/devops/changelog
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill changelog-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing changelogs from git history is tedious and error-prone. This Skill automates the process by parsing conventional commits and producing a structured CHANGELOG.md in Keep a Changelog format. ## Core Features & Use Cases - Conventional Commit Parsing: Extracts commit types (feat, fix, docs, refactor, perf, test, chore, breaking, security) and groups them into Added, Fixed, Changed, Security, and Other sections. - Flexible Version Ranges: Generate from the last tag to HEAD, between two tags, initialize a new CHANGELOG.md, or add an Unreleased section. - Use Case: Before cutting a v1.2.0 release, run the changelog command to automatically compile all commits since v1.1.0 into a properly formatted release section with PR/issue references preserved. ## Quick Start Ask Claude to generate a changelog from the last git tag to HEAD using conventional commits in Keep a Changelog format.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from git commits?▼

Run the changelog command to parse commits from the last tag to HEAD. It extracts conventional commit prefixes like feat and fix, groups them into categories, and writes a Keep a Changelog formatted section into CHANGELOG.md.

How to create a changelog for a specific version range?▼

Pass a git range such as v1.0.0..v1.1.0 to the changelog command. It runs git log over that range, parses the conventional commit messages, and generates the release section only for those commits.

What commit format does changelog generation require?▼

It works best with conventional commits using prefixes like feat:, fix:, docs:, refactor:, perf:, test:, chore:, breaking:, and security:. Non-conventional commits are grouped under Other or skipped.

Can I create a new CHANGELOG.md from scratch?▼

Yes, use the --init flag to create a new CHANGELOG.md with the Keep a Changelog header and Semantic Versioning notice. You can also use --unreleased to add an Unreleased section to an existing file.

What happens if my repository has no git tags?▼

The skill relies on git describe and tag listing to find version boundaries. Without tags, there is no last-tag reference point, so you should specify an explicit commit range or initialize a new changelog first.

Related Skills

Explore More Software Engineering Skills→
gaebalaigaebalai
2

release-tag-plan

Plan release tagging and CHANGELOG strategy using semantic versioning.

Community
Advanced
dropseeddropseed
1.0k

plainx-release

Bump versions, generate changelogs, and tag Git releases for Python packages.

Official
Advanced
vm0-aivm0-ai
1.1k

commit

Run format, lint, type-check, and test steps before Git commits.

Official
Intermediate
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced