changelog-automation

Automates changelog generation from commits and releases following Keep a Changelog format.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill changelog-automation-5onyy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-automation
Source: https://github.com/5onyy/essential-ai-agent-skills/tree/main/.cursor/skills/changelog-automation
Command: npx skills add https://github.com/5onyy/essential-ai-agent-skills --skill changelog-automation-5onyy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing changelogs and release notes is error-prone and inconsistent, especially when commit history is messy or versioning rules are unclear. This Skill standardizes changelog generation, commit conventions, and semantic versioning across a project. ## Core Features & Use Cases - Automated Changelog Generation: Generate Keep a Changelog-compliant files from conventional commits using standard-version, semantic-release, git-cliff, or commitizen. - Commit Convention Enforcement: Set up commitlint with Husky hooks to validate Conventional Commits before they land. - CI/CD Release Workflows: Configure GitHub Actions pipelines that bump versions, generate release notes, and publish GitHub Releases automatically. - Use Case: A team wants every merge to main to produce a versioned release with categorized notes (Features, Bug Fixes, Performance). This Skill guides them through configuring semantic-release with commit-analyzer and changelog plugins. ## Quick Start Set up automated changelog generation for my Node.js project using conventional commits and standard-version.

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?▼

Use tools like standard-version, semantic-release, or git-cliff that parse Conventional Commits and generate a Keep a Changelog-formatted file. Commit types like feat and fix map to changelog sections such as Added and Fixed automatically.

What is the difference between standard-version and semantic-release?▼

standard-version runs locally or on demand, bumping versions and updating CHANGELOG.md via npm scripts. semantic-release runs fully automated in CI, analyzing commits, publishing packages, and creating GitHub releases without manual triggers.

How do I enforce conventional commit messages in my team?▼

Install commitlint with the conventional config and add a Husky commit-msg hook that runs commitlint on every commit. Invalid messages are rejected before the commit is created, keeping history machine-parseable.

Can I generate changelogs in a Python project?▼

Yes, use commitizen with the cz_conventional_commits plugin configured in pyproject.toml. Running cz bump --changelog updates the version, tags the release, and appends entries to the changelog.

When should I not automate changelog generation?▼

Avoid automation when the project has no release process or versioning, when you only need a one-time manual release note, or when commit history is unavailable or unreliable for parsing.