release-changelog

Generate structured markdown release changelogs from git history and pull requests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Nirpat3/MIB007 --skill release-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-changelog
Source: https://github.com/Nirpat3/MIB007/tree/main/skills/release-changelog
Command: npx skills add https://github.com/Nirpat3/MIB007 --skill release-changelog

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, pull requests, and changeset files, saving significant manual effort and ensuring consistency.

Core Features & Use Cases

  • Automated Changelog Generation: Reads git history, merged PRs, and changeset files to compile release notes.
  • Breaking Change Detection: Identifies breaking changes through migration files, schema modifications, API route changes, and commit conventions.
  • 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 releases/v{version}.md file, ensuring all significant changes are documented accurately and presented clearly to users.

Quick Start

Use the release-changelog skill to generate the changelog for the next release.

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 from git history and merged pull requests?

Generate release notes by analyzing git history, merged pull requests, and changeset files since the last release tag to automatically compile structured markdown changelogs. This process detects breaking changes and categorizes modifications into highlights, improvements, and fixes.

What is the best way to detect breaking changes for a changelog from recent commits?

Detect breaking changes for a changelog by analyzing migration files, schema modifications, API route changes, and commit conventions within your git history. This automated detection ensures critical updates are highlighted before outputting the final release markdown.

How do I categorize software release notes into structured markdown automatically?

Categorize software release notes into structured markdown by reading changeset files and git history, then grouping modifications into Breaking Changes, Highlights, Improvements, and Fixes before saving the output to releases/v{version}.md.

Can I use changeset files to prepare a draft for the next software release?

Yes, you can use changeset files alongside merged pull requests and git history to prepare the next software release. This automatically drafts the releases/v{version}.md file, ensuring all significant changes are documented accurately and presented clearly to users.

Does automated changelog generation work without manual commit message formatting?

Automated changelog generation primarily relies on analyzing changeset files, merged pull requests, and git history. While it detects breaking changes through migration files, schema modifications, and API route changes, standardizing commit conventions improves categorization accuracy.