home / skills / sickn33 / antigravity-awesome-skills / changelog-automation

changelog-automation skill

safe

This skill automates changelog generation from commits, PRs, and releases using Keep a Changelog format to streamline release notes.

This is most likely a fork of the changelog-automation skill from vaayne

npx playbooks add skill sickn33/antigravity-awesome-skills --skill changelog-automation

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.2 KB

---
name: changelog-automation
description: 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.
---

# Changelog Automation

Patterns and tools for automating changelog generation, release notes, and version management following industry standards.

## Use this skill when

- Setting up automated changelog generation
- Implementing conventional commits
- Creating release note workflows
- Standardizing commit message formats
- Managing semantic versioning

## Do not use this skill when

- The project has no release process or versioning
- You only need a one-time manual release note
- Commit history is unavailable or unreliable

## Instructions

- Select a changelog format and versioning strategy.
- Enforce commit conventions or labeling rules.
- Configure tooling to generate and publish notes.
- Review output for accuracy, completeness, and wording.
- If detailed examples are required, open `resources/implementation-playbook.md`.

## Safety

- Avoid exposing secrets or internal-only details in release notes.

## Resources

- `resources/implementation-playbook.md` for detailed patterns, templates, and examples.

Overview

This skill automates changelog generation from commits, pull requests, and releases using the Keep a Changelog format. It streamlines release-note creation, enforces commit conventions, and integrates with CI/CD to produce consistent, reviewable notes for each release. Use it to standardize versioning and save time during release cycles.

How this skill works

The skill scans git history, commit messages, PR titles, and release metadata to build a structured changelog following Keep a Changelog sections (Added, Changed, Fixed, etc.). It supports conventional commit parsing, label mapping, and semantic version bump detection, then formats entries into markdown and can push the changelog or release notes to a repository or release page. Hooks and CI actions allow automated runs on merges, tags, or manual triggers.

When to use it

Setting up automated release workflows for multi-developer projects
Enforcing conventional commits and consistent changelog sections
Generating release notes from merged PRs and commit history
Standardizing semantic versioning and automated version bumps
Publishing formatted changelogs to releases or documentation sites

Best practices

Choose a clear commit convention (Conventional Commits recommended) and document it in contributing guidelines
Map repository labels to changelog sections to capture PR intent reliably
Run changelog generation in CI on release tags or merge-to-main events and require a human review before publishing
Strip or redact secrets and internal-only identifiers from generated notes before publishing
Keep a small, curated set of changelog categories to avoid noisy or ambiguous entries

Example use cases

Automate release notes generation for a monthly product release pipeline
Enforce commit message format in pull request templates and generate changelog items automatically
Create a CI job that updates CHANGELOG.md and creates a GitHub release when a semver tag is pushed
Aggregate PR labels across multiple repositories to produce consolidated release summaries
Convert an existing commit history into an initial Keep a Changelog file during project onboarding

FAQ

What input formats does this skill accept?

It parses git commits, PR titles/bodies, labels, and release tags; conventional commit messages are supported for best results.

Can it automate semantic version bumps?

Yes. It can detect BREAKING CHANGES,feat,fix scopes and suggest or apply major/minor/patch version bumps in CI.