Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
wshobson avatar

Changelog Automation

  • 10.9k installs
  • 38.3k repo stars
  • Updated July 22, 2026
  • wshobson/agents

How to automate changelog generation from git commits, PRs, and releases using Conventional Commits and Keep a Changelog standards.

About

This skill teaches patterns and tools for automating changelog generation, release notes, and version management following industry standards like Keep a Changelog and Conventional Commits. Developers use it when setting up release workflows, implementing commit message standards, and generating GitHub/GitLab release notes. Key workflows include writing scoped commit messages (e.g. feat(auth), fix(checkout)), marking breaking changes with `!` or footer, referencing issues in commits, and validating commits via commitlint in CI pipelines. The skill covers semantic versioning integration, structured release note templates with highlights and upgrade guides, and best practices like one logical change per commit and never manually editing generated changelogs.

  • Keep a Changelog format with sections for features, fixes, breaking changes, and upgrade guides
  • Conventional Commits syntax (feat, fix, type!) enables automated changelog generation from git history
  • Commit validation via commitlint in CI pipelines prevents non-standard messages
  • Semantic versioning alignment for automated version bumping based on change types
  • Scoped commit messages (auth, checkout, api) organize changes by functional area

Changelog Automation by the numbers

  • 10,904 all-time installs (skills.sh)
  • +229 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #1 of 257 Release Management skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

changelog-automation capabilities & compatibility

Capabilities
parse git commit history into structured changel · validate commits against conventional commits sp · generate release notes with highlights and break · automate semantic version bumping · integrate with ci/cd pipelines
Works with
github · gitlab · bitbucket
Use cases
documentation · ci cd · code review
Platforms
macOS · Windows · Linux
Runs
Runs locally
Pricing
Free
From the docs

What changelog-automation says it does

feat(auth): add OAuth2 support for Google login
skill:wshobson/agents#changelog-automation
npx skills add https://github.com/wshobson/agents --skill changelog-automation

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs10.9k
repo stars38.3k
Security audit2 / 3 scanners passed
Last updatedJuly 22, 2026
Repositorywshobson/agents

What it does

Automate changelog and release notes generation from commits and PRs using Conventional Commits and Keep a Changelog format.

Who is it for?

Teams implementing release workflows, standardizing commit conventions, automating release notes, managing semantic versioning at scale.

Skip if: Single-file scripts, projects with no formal release process, teams not ready to adopt commit message standards.

When should I use this skill?

Setting up CI/CD release automation, establishing commit message conventions, creating release note templates, integrating with GitHub/GitLab.

What you get

Developers can generate standardized, complete changelogs automatically from structured commits, reducing manual work and improving release note quality.

  • Standardized commit message format
  • Automated changelog generation workflow
  • Release note templates

By the numbers

  • Keep a Changelog format includes 8 standard sections: Unreleased, versions with added/changed/deprecated/removed/fixed/s
  • Conventional Commits types covered: feat, fix, with optional scope and breaking change marker

Files

SKILL.mdMarkdownGitHub ↗

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

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

## Summary

This release introduces dark mode support and improves checkout performance
by 40%. It also includes important security updates.

## Highlights

### 🌙 Dark Mode

Users can now switch to dark mode from settings. The preference is
automatically saved and synced across devices.

### ⚡ Performance

- Checkout flow is 40% faster
- Reduced bundle size by 15%

## Breaking Changes

None in this release.

## Upgrade Guide

No special steps required. Standard deployment process applies.

## Known Issues

- Dark mode may flicker on initial load (fix scheduled for v2.1.1)

## Dependencies Updated

| Package | From    | To      | Reason                   |
| ------- | ------- | ------- | ------------------------ |
| react   | 18.2.0  | 18.3.0  | Performance improvements |
| lodash  | 4.17.20 | 4.17.21 | Security patch           |

Commit Message Examples

# Feature with scope
feat(auth): add OAuth2 support for Google login

# Bug fix with issue reference
fix(checkout): resolve race condition in payment processing

Closes #123

# Breaking change
feat(api)!: change user endpoint response format

BREAKING CHANGE: The user endpoint now returns `userId` instead of `id`.
Migration guide: Update all API consumers to use the new field name.

# Multiple paragraphs
fix(database): handle connection timeouts gracefully

Previously, connection timeouts would cause the entire request to fail
without retry. This change implements exponential backoff with up to
3 retries before failing.

The timeout threshold has been increased from 5s to 10s based on p99
latency analysis.

Fixes #456
Reviewed-by: @alice

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

Related skills

How it compares

Pick changelog-automation when release notes must be derived from git commits; use general documentation skills when writing narrative product docs unrelated to version history.

FAQ

What is Conventional Commits?

Syntax for commit messages (feat, fix, type!) that enables automated changelog generation and semantic versioning. Example: feat(auth): add OAuth2 support.

How do I mark breaking changes?

Use `!` after type/scope (feat(api)!: change response format) or add BREAKING CHANGE: footer in commit body with migration guide.

What is commitlint?

Tool that validates commit messages match Conventional Commits format in CI pipelines, preventing non-standard commits from merging.

Is Changelog Automation safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.