changelog-automation

Generate changelogs from git commits using Keep a Changelog and Conventional Commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation and maintenance of changelogs, ensuring consistency and saving developers time by adhering to industry standards like Keep a Changelog and Conventional Commits.

Core Features & Use Cases

  • Automated Changelog Generation: Generate changelogs from commit history.
  • Conventional Commits Enforcement: Integrate tools to enforce commit message standards.
  • Semantic Versioning: Manage versioning automatically based on commit types.
  • Use Case: Streamline your release process by automatically generating release notes for each new version based on the commits made since the last release.

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 automate changelog generation from git commits?

Automate changelog generation from git commits by parsing commit history using Conventional Commits standards and Keep a Changelog format. Tools like standard-version, semantic-release, or git-cliff extract commit metadata to automatically compile structured release notes for each new version.

What is the best way to enforce Conventional Commits for semantic versioning?

Enforce Conventional Commits for semantic versioning by integrating commitlint or commitizen into your workflow. These tools validate commit message formats and automatically determine version bumps based on commit types like feat or fix, ensuring standardized release notes.

Can I use semantic-release with GitHub Actions workflows?

Yes, semantic-release integrates with GitHub Actions workflows to automate changelog generation. By configuring the semantic-release workflow in your repository, you can automatically generate release notes, update the changelog, and publish new versions upon merging commits.

Does git-cliff support Keep a Changelog format?

Yes, git-cliff supports Keep a Changelog format. It parses conventional commit history and generates customized changelogs adhering to industry standards like Keep a Changelog, providing a Rust-based approach to standardize release notes and version management.

How do commitizen and commitlint differ for changelog automation?

Commitizen is a Python-based tool guiding interactive commit creation and changelog generation, while commitlint focuses on linting commit messages against standards. Both facilitate changelog automation by enforcing Conventional Commits, ensuring commit history consistency for automated release notes.