skills.rest
hpsgd
hpsgdOFFICIAL
Explore all skills by this author →
WebsiteGitHub

write-changelog

Generate structured changelogs from Git history and PR merges.

Updated Apr 1, 2026
Search Tags:#automation#git#changelog#versioning#documentation#breaking-changes#release-notes
One-click install
npx skills add https://github.com/hpsgd/claude-marketplace --skill write-changelog-hpsgd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-changelog
Source: https://github.com/hpsgd/claude-marketplace/tree/main/plugins/product/internal-docs-writer/skills/write-changelog
Command: npx skills add https://github.com/hpsgd/claude-marketplace --skill write-changelog-hpsgd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog maintenance for software projects is often tedious, error-prone, and hard to keep stakeholders aligned. This skill automates extracting changes from Git history and PRs to produce a concise, versioned changelog that suits both users and developers.

Core Features & Use Cases

  • Automated grouping: classify commits into Added, Changed, Fixed, Removed, Deprecated, and Security sections.
  • Version-aware output: generate entries per release with migration notes and explicit breaking-change indicators.
  • Audience-aware formatting: tailor user-facing notes for customers or developers, with optional summaries.
  • Use Case: generate release notes for a new software version from a repository's commit history and PR merges.

Quick Start

Request a changelog for the current repository using the default HEAD range.

Frequently Asked Questions about write-changelog

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

FAQPage Schema
How do I generate a changelog from git history automatically?▼

You can generate a changelog from git history by automating the extraction of commits and PR merges. This process classifies changes into structured sections like Added, Changed, and Fixed to produce a concise, versioned release document.

What is the best way to group git commits into a structured changelog?▼

Grouping git commits into a structured changelog involves classifying changes into Added, Changed, Fixed, Removed, Deprecated, and Security sections. This approach organizes release notes to suit both user-facing and technical developer audiences.

How do I document breaking changes and migration notes in release notes?▼

Documenting breaking changes in release notes requires generating version-aware changelog entries with explicit breaking-change indicators. The output includes specific migration notes alongside the categorized software changes for each release.

Can I format release notes differently for users versus developers?▼

Formatting release notes for different audiences is supported through audience-aware formatting. You can tailor the generated output to provide user-facing summaries for customers or detailed technical documentation for developers.

Do I need a specific Git workflow to extract PR merges for a changelog?▼

Extracting PR merges for a changelog relies on standard Git history and a user-provided list of changes. It processes the repository's commit history and merge records to automate the generation of structured release documentation.

Related Skills

Explore More Software Engineering Skills→
k97k97
4

gen-release-notes

Generate structured release notes from git commit history and pull request data.

Community
Advanced
frostantfrostant
42

changelog-generator

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

Community
Intermediate
sunholo-datasunholo-data
33

AILANG Release Manager

Automates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.

Official
Intermediate
wibus-weewibus-wee
54

changelog

Generates changelogs from Git commits and PRs for release notes.

Community
Intermediate