CClaude Code Catalog
All Skills

Changelog Automation

ProductivityBeginner

Analyzes commit history and PR info to auto-generate user-friendly changelogs. Includes SemVer-based version suggestions and category-based grouping.

Trigger/changelog
FrequencyOn deploy

Open source maintainer? Run /changelog to auto-generate release notes from commits

PM writing release announcements? Convert technical commit messages into user-friendly language

ChangelogReleaseVersion ControlAutomation

How It Works

Run /changelog -> analyze commit history
Phase 1: 3 classification tasks in parallel
feature-group
Group new features
fix-group
Group bug fixes
breaking-detect
Detect breaking changes
Suggest SemVer version + generate markdown
CHANGELOG.md update + version tag

Skill Code

# Changelog Generator Skill ## Trigger: /changelog [since tag or date] When invoked: 1. Analyze commits since last release: - `git log [last-tag]..HEAD` - Parse conventional commit prefixes - Group by type (feat, fix, refactor, etc.) 2. Determine version bump: - Breaking change → Major (X.0.0) - New feature → Minor (0.X.0) - Bug fix → Patch (0.0.X) 3. Generate changelog: --- ## [version] — [YYYY-MM-DD] ### ✨ New Features - [feature description] ([#PR]) ### 🐛 Bug Fixes - [fix description] ([#PR]) ### ♻️ Improvements - [improvement description] ### ⚠️ Breaking Changes - [what changed + migration guide] --- 4. Optionally update CHANGELOG.md and create git tag

Copy and paste into your CLAUDE.md to start using immediately.

How Changelog Automation Works

Changelog Generator reads git history between two tags or commits, categorizes changes by type (features, fixes, breaking changes), groups them logically, and formats output following the Keep a Changelog convention.

When to Use Changelog Automation

Transforms the tedious release preparation process into a one-command operation — especially valuable for projects with frequent releases where manually writing changelogs would consume significant time each cycle.

Key Strengths

  • Auto-categorizes commits into features, fixes, and breaking changes
  • Follows Keep a Changelog convention for professional output
  • Groups related changes logically for readability
  • One command replaces hours of manual changelog writing

Popular in Other Categories