changelog-automation

Automates changelog and release notes generation from Conventional Commits.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill changelog-automation-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/documentation-generation/skills/changelog-automation
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill changelog-automation-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates changelog generation from commits, PRs, and releases following Keep a Changelog standards.

Core Features & Use Cases

  • Keeps a standardized changelog by following the Keep a Changelog format.
  • Integrates with Conventional Commits and Semantic Versioning to automate release notes.
  • Supports multiple tooling options (conventional changelog, standard-version, semantic-release, git-cliff, commitizen) for flexible workflows.

Quick Start

Run the automated workflow to generate and publish a changelog according to Conventional Commits and Keep a Changelog standards.

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 conventional commits?

Automate changelog generation by parsing conventional commits to produce structured release notes following the Keep a Changelog format. The workflow integrates semantic versioning to ensure consistent version bumps alongside automated changelog updates across local scripts or CI pipelines.

What is the Keep a Changelog format and when do I need it for release notes?

Keep a Changelog is a standardized format for maintaining human-readable release notes. You need it when automating changelog generation from commits and releases to ensure consistent structure, categorizing changes into added, changed, deprecated, removed, fixed, and security sections.

Does semantic-release work with Keep a Changelog standards in CI pipelines?

Yes, semantic-release is supported alongside standard-version, conventional changelog, git-cliff, and commitizen. These tools integrate within CI pipelines to automate semantic versioning and enforce strict changelog structure according to Keep a Changelog and Conventional Commits standards.

What's the best way to set up automated release notes with GitHub Actions?

Set up automated release notes by integrating GitHub Actions with conventional changelog tooling to parse commit messages and generate structured output. The workflow applies semantic versioning rules and Keep a Changelog templates to publish standardized release notes automatically.

Can I use git-cliff to generate a changelog from conventional commits?

Yes, git-cliff is one of the supported tooling options for changelog automation. It parses conventional commits to generate changelogs and release notes while maintaining compatibility with semantic versioning and the Keep a Changelog format across various workflow implementations.

Why does my automated changelog not follow the Keep a Changelog structure correctly?

Automated changelogs deviate from the Keep a Changelog structure when commit messages fail to follow Conventional Commits standards. Enforcing commit message conventions through commitizen and applying strict changelog templates ensures the generated output adheres to the required standardized format.