changelog-automation

Generate changelogs from commit history using Keep a Changelog and Conventional Commits.

2|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/as4584/antigravity-skills --skill changelog-automation-as4584
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/as4584/antigravity-skills/tree/main/agents-wshobson/plugins/documentation-generation/skills/changelog-automation
Command: npx skills add https://github.com/as4584/antigravity-skills --skill changelog-automation-as4584

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of generating changelogs, ensuring consistency and saving development time by standardizing release notes based on commit history.

Core Features & Use Cases

  • Automated Changelog Generation: Creates changelogs in the Keep a Changelog format from commit messages.
  • Conventional Commits Enforcement: Supports and leverages Conventional Commits for structured commit messages.
  • Semantic Versioning: Integrates with semantic versioning practices for release management.
  • Use Case: When preparing for a new software release, use this Skill to automatically generate the release notes by analyzing the commit history since the last release, ensuring all new features, bug fixes, and breaking changes are accurately documented.

Quick Start

Use the changelog-automation skill to generate a changelog from your git commits.

Frequently Asked Questions about changelog-automation

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

FAQPage Schema
How do I generate a changelog from git commit history automatically?

Automated changelog generation parses git commit history to produce standardized release notes. This Skill analyzes Conventional Commits messages to build a Keep a Changelog formatted document, ensuring consistent documentation for new releases.

What is the best way to enforce Conventional Commits for release notes?

Enforcing Conventional Commits standardizes commit messages to automate release notes generation. This Skill leverages structured commit formats to accurately categorize features, fixes, and breaking changes for semantic versioning.

Can I use semantic-release or standard-version for automated changelog generation?

Yes, semantic-release and standard-version are supported for automated changelog generation. This Skill integrates these Node.js tools, alongside Rust-based git-cliff and Python's commitizen, to facilitate standardized release notes and version management.

Does git-cliff support Keep a Changelog format for Rust projects?

Git-cliff supports Keep a Changelog format by parsing Conventional Commits from your repository. This Skill includes git-cliff as a supported implementation method to generate standardized release notes for Rust and other projects.

Why do I need Conventional Commits for semantic versioning?

Conventional Commits provide the structured commit message format required to automate semantic versioning. This Skill uses these structured messages to determine version bumps and automatically document features, bug fixes, and breaking changes in the changelog.

What are the limitations of automating changelog generation from commit messages?

Automating changelog generation requires strict adherence to Conventional Commits standards; unstructured commit messages will not parse correctly. This Skill depends on consistent commit history to accurately map changes to Keep a Changelog formats and semantic versioning.