skills.rest
Dinuda
DinudaCOMMUNITY
Explore all skills by this author →
𝕏@Dinuda3GitHub

release-changelog

Generate stable release changelogs from git commits, changesets, and merged PRs.

Updated Mar 11, 2026
Search Tags:#automation#git#changelog#developer tools#documentation#release notes
One-click install
npx skills add https://github.com/Dinuda/summun.cloud --skill release-changelog-dinuda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/Dinuda/summun.cloud/tree/main/skills/release-changelog
Command: npx skills add https://github.com/Dinuda/summun.cloud --skill release-changelog-dinuda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of user-facing changelogs for software releases, ensuring consistency and saving developers time.

Core Features & Use Cases

  • Automated Changelog Generation: Creates changelogs based on git commits, changesets, and PRs.
  • Breaking Change Detection: Identifies and categorizes breaking changes for clear user communication.
  • Use Case: After merging a new feature and several bug fixes, run this Skill to generate the releases/vX.Y.Z.md file, ready for review and release.

Quick Start

Generate the changelog for the next release using the release-changelog skill.

Frequently Asked Questions about release-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes automatically from git commits?▼

You can generate release notes automatically by running a tool that analyzes git commits, changesets, and merged PRs since the last stable tag to categorize updates into sections like Improvements and Fixes.

Can I detect breaking changes automatically when creating a changelog?▼

Yes, automated changelog generation can detect breaking changes by analyzing git commits and merged PRs, explicitly categorizing them to ensure clear user communication in the final release notes.

What is the best way to structure automated changelogs for software releases?▼

The best way to structure automated changelogs is to categorize analyzed git commits and PRs into predefined sections such as Improvements and Fixes, outputting the results to a versioned markdown file.

How does a changelog generator handle merged PRs and changesets?▼

A changelog generator handles merged PRs and changesets by analyzing them alongside git commits since the last stable tag, detecting breaking changes, and sorting the entries into predefined categories.

Do I need a specific git tag format to automate release notes generation?▼

You need a previous stable git tag to anchor the automation, as the changelog generator analyzes commits, changesets, and PRs made since that last stable tag to build the new release notes.

Related Skills

Explore More Software Engineering Skills→
kagentikagenti
16

release-notes

Generate Markdown release notes from merged PRs between version tags.

Official
Intermediate
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
aaaa47080aaaa47080
4

release

Automate git releases with changelog generation and semantic versioning.

Community
Intermediate
PicoMLXPicoMLX

app-store-changelog

Generate App Store release notes from git commit history.

Official
Intermediate