skills.rest
tbuijibing
tbuijibingCOMMUNITY
Explore all skills by this author →
GitHub

release-changelog

Generate structured markdown release changelogs from git history and merged PRs.

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

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 release changelogs by analyzing git history, merged pull requests, and changeset files, ensuring consistent and comprehensive release notes.

Core Features & Use Cases

  • Automated Changelog Generation: Reads git history, PRs, and changesets to compile release notes.
  • Breaking Change Detection: Identifies and flags breaking changes based on commit messages, migration files, and schema modifications.
  • Categorization: Organizes changes into 'Breaking Changes', 'Highlights', 'Improvements', and 'Fixes'.
  • Use Case: When preparing for a new software release, use this Skill to automatically draft the vX.Y.Z.md file in the releases/ directory, which can then be reviewed and finalized.

Quick Start

Generate a changelog for the next release by running 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 automate release changelog generation from git history and merged PRs?▼

To automate release changelog generation, this Skill analyzes git history, merged pull requests, and changeset files since the last release tag. It then categorizes changes and outputs a structured markdown draft to the releases/v{version}.md file.

How does breaking change detection work when drafting release notes?▼

Breaking change detection works by scanning commit messages, migration files, and schema modifications during the changelog generation process. It identifies and flags these changes, placing them in a dedicated 'Breaking Changes' category in the output.

Can I use this to categorize changes into sections like Improvements and Fixes?▼

Yes, you can use this Skill to categorize changes into structured sections. It automatically organizes analyzed git history and changesets into 'Breaking Changes', 'Highlights', 'Improvements', and 'Fixes' within the markdown output.

Does the generated changelog file require human review before publishing?▼

Yes, the generated changelog file requires human review before finalization. The Skill outputs a structured markdown draft to releases/v{version}.md, ensuring developers can verify accuracy and context before the release notes are published.

What is the best way to generate a vX.Y.Z.md file for a new software release?▼

The best way to generate a vX.Y.Z.md file is to run this Skill against your repository. It reads changesets and merged PRs since the last release tag to automatically draft the markdown file directly in your releases/ directory.

Related Skills

Explore More Software Engineering Skills→
thetangstrthetangstr

release-changelog

Compile commit history, pull requests, and changeset data into structured changelog reports.

Community
Basic
pythoninthegrassespythoninthegrasses
1

changelog-automation

Generate changelogs and release notes from commits, PRs, and tags.

Official
Advanced
EndstoneMCEndstoneMC
715

release

Automate Endstone Minecraft Bedrock server releases with versioning, CHANGELOG updates, and CI/CD triggers.

Official
Advanced
Doyajin174Doyajin174
1

changelog-generator

Convert git commit history into categorized Markdown release notes.

Community
Intermediate