Agent skill · software engineering · aiskillstore
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
Why this skill is useful
Adds specific automation scripts and configuration for changelog generation that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Changelog Automation Patterns and tools for automating changelog generation, release notes, and version management following industry standards. When to Use This Skill Setting up automated changelog generation Implementing Conventional Commits Creating release note workflows Standardizing commit message formats Generating GitHub/GitLab release notes Managing semantic versioning Core Concepts 1. Keep a Changelog Format 2. Conventional Commits Type Description Changelog Section ------ ------------- ------------------- feat New feature Added fix Bug fix Fixed docs Documentation (usually excluded) style Formatting (usually excluded) refactor Code restructure Changed perf Performance Changed test Tests (usually excluded) chore Maintenance (usually excluded) ci CI changes (usually excluded) build Build system (usually excluded) revert Revert commit Removed 3. Semantic Versioning Implementation Method 1: Conventional Changelog (Node.js) Method 2: standard-version Configuration Method 3: semantic-release (Full Automation) Method 4: GitHub Actions Workflow Method 5: git-cliff (Rust-based, Fast) Method 6: Python (commitizen) Release Notes Templates GitHub Release Template Internal Release Notes Commit Message Examples Best Practices Do's Follow Conventional Commits - Enables automation Write clear messages - Future you will thank you Reference issues - Link commits to tickets Use scopes consistently - Define team conventions Automate releases - Reduce manual errors Don'ts Don't mix changes - One logical change per commit Don't skip validation - Use commitlint Don't manual edit - Generated changelogs only Don't forget breaking changes - Mark with ! or footer Don't ignore CI - Validate commits in pipeline Resources Keep a Changelog Conventional Commits Semantic Versioning semantic-release git-cliff
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/changelog-automation--e3f0ac