skills.rest
plwsdytcj
plwsdytcjCOMMUNITY
Explore all skills by this author →
GitHub

release-changelog

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

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

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 informative release notes.

Core Features & Use Cases

  • Automated Changelog Generation: Reads git history and structured data to compile release notes.
  • Breaking Change Detection: Identifies and flags breaking changes based on commit messages, migrations, and API modifications.
  • Categorization: Organizes changes into Breaking, Highlights, Improvements, and Fixes.
  • Use Case: When preparing for a new software release, use this Skill to automatically draft the changelog, saving developers significant time and ensuring all relevant changes are captured.

Quick Start

Use the release-changelog skill to generate the changelog for version 0.3.0.

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 automatically?▼

To generate release notes automatically, this Skill parses git commit history, merged pull requests, and changeset files to detect breaking changes and categorize modifications into structured markdown.

How does breaking change detection work when generating a changelog?▼

Breaking change detection for changelog generation works by analyzing commit messages, migrations, and API modifications to identify and flag alterations that may impact existing functionality.

Can I use GitHub CLI to pull merged pull requests for changelog generation?▼

Yes, you can use GitHub CLI optionally for comprehensive data gathering when generating changelogs, pulling merged pull requests alongside git history and changeset files to compile release notes.

What's the best way to categorize software release notes into structured sections?▼

The best way to categorize release notes is by organizing detected changes into structured sections such as Breaking, Highlights, Improvements, and Fixes, outputting the results as a markdown file.

Do I need git CLI installed to generate release changelogs?▼

Yes, you need git CLI installed and available in your environment, as the Skill requires it to parse repository history and detect changes for release documentation generation.

Related Skills

Explore More Software Engineering Skills→
thetangstrthetangstr

release-changelog

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

Community
Basic
pwarnockpwarnock
2

release-publishing

Automate release planning and publishing workflows with Changesets and semantic versioning.

Community
Intermediate
yongwoonyongwoon
8

ywc-changelog-release-notes

Generate CHANGELOG.md entries and release notes from git history and merged pull requests.

Community
Intermediate
tapanshahtapanshah

Changelog Generator

Generate markdown and JSON changelog entries from Conventional Commits.

Community
Advanced