Release Changelog from Commits and PRs

Turns a commit range or merged PRs into a release changelog with breaking changes, migration steps, and user-facing wording.

Development / Documentationchangelogrelease-notes
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Generate a changelog entry from our last 20 commits”
Beforegeneric AI agent
I can help you write a changelog. Typically, you'd want to go through your recent commits and group them by type—features, bug fixes, improvements. You might organize by component or by impact. I'd be happy to help you draft something if you share what changed, or I could suggest a format that works well. The key is making it readable for your users while capturing the important updates.
Afterwith Release Changelog from Commits and PRs
CHANGELOG - Version 2.3.0

FEATURES
• Added real-time event streaming API for subscriber feeds (commits ca7f3e, 8b2a14)
• Implemented batch export to CSV with configurable column selection (9d4c82)
• New analytics dashboard showing 7-day trending content by category (f1e7c3)

BUG FIXES
• Fixed race condition in user session refresh on parallel requests (ae3b91)
• Corrected timezone handling for event timestamps in stored reports (2c5b77)
• Resolved memory leak in WebSocket connection handler (d9a22f)

IMPROVEMENTS
• Performance: Reduced API latency by 34% via query optimization (5e8d41, 7a2b9c)
• Updated error messages for clarity on rate-limit failures (3f6e1a)
• Deprecated legacy OAuth 1.0 endpoints; migrate to OAuth 2.0 before Aug 2026

This changelog is ready to publish as-is. Customize the format or add context as needed.

About this skill

Your release notes are either raw commit messages nobody can read, or a hand-written summary that missed the one change that broke everyone's config. This skill reads a commit range or merged PR list, works out what each change means for someone upgrading, and writes a changelog you can paste straight into CHANGELOG.md or a release page.

What it does

  • Classifies changes by what users experience, not by commit prefix, so internal feat: commits stay out and behavior-changing fix: commits get flagged
  • Hunts for breaking changes that were never labeled: renamed env vars, changed defaults, dropped runtime versions, new validation, response shape changes
  • Writes a before/after and a concrete migration step for every breaking change
  • Collapses multi-commit features into one entry and drops fixes for bugs that never shipped
  • Rewrites commit-speak into the symptom users actually saw
  • Checks your proposed version number against the changes and suggests the correct SemVer bump

What you get

A paste-ready changelog section in Keep a Changelog format, plus a separate reviewer note listing what was omitted, which commits were too vague to classify, and the suggested version.

Best for

Maintainers of libraries, CLIs, and apps who cut releases from git history and want accurate notes without spending an hour rewriting commit messages.

SKILL.md preview

SKILL.md
---
name: release-changelog-from-commits
description: Turns a commit range, git log, or list of merged PRs into a publishable changelog entry by classifying each change by its user-visible effect, collapsing related commits, detecting breaking changes with a checklist, and writing migration steps. Use when the user says "write the changelog for v2.4", "turn these commits into release notes", "what changed since the last tag", "generate CHANGELOG.md from git log", "summarize these merged PRs for the release", "our release notes are just raw commit messages", or "we keep forgetting to mention breaking changes".
---

# Release Changelog from Commits and PRs

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More development skills

View all Development skills →