write-changelog

Convert pull request IDs or requirements files into dated Markdown changelog entries.

Updated Mar 2, 2026

Search Tags:#changelog #documentation #writing #github #requirements #pr #release-notes

Ready to run

npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill write-changelog-alexmensch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-changelog
Source: https://github.com/alexmensch/claude-sdlc-plugins/tree/main/plugins/documentation/skills/write-changelog
Command: npx skills add https://github.com/alexmensch/claude-sdlc-plugins --skill write-changelog-alexmensch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts pull requests and requirements files into concise, user-facing changelog entries so product teams can communicate what changed without exposing implementation details.

Core Features & Use Cases

PR context extraction: Reads PR title, body, and merge date, checks merge status, and follows embedded requirements GUIDs to find linked product files.
Requirements file support: Reads product requirements files to extract feature summaries and requirement tables as source context.
Changelog authoring and save workflow: Produces a single entry with Title, Date, and a 2–4 sentence Description, offers to save the entry as a dated Markdown file, and writes files using a YYYY-MM-DD-<slug>.md filename format when requested.
Use case: Turn one or several merged PRs or product requirement documents into a brief release note entry suitable for a public changelog.

Quick Start

Write a brief, user-facing changelog entry summarizing PR #47 and save it to the changelog/ directory.

Frequently Asked Questions about write-changelog

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

FAQPage Schema

How do I generate user-facing release notes from merged GitHub PRs?▼

To generate user-facing release notes from GitHub PRs, provide the pull request IDs to extract metadata, verify merge dates, and summarize the changes into a concise 2–4 sentence description suitable for a public changelog.

What is the best way to turn product requirement documents into a changelog entry?▼

Turning product requirement documents into a changelog entry involves reading the requirements files to extract feature summaries and requirement tables, then assembling the extracted context into a brief, user-facing release note.

Can I save generated changelog entries as Markdown files?▼

Yes, you can save generated changelog entries as Markdown files. The skill offers to write the output using a YYYY-MM-DD-<slug>.md filename format when saving to a specified directory.

Does this changelog writing process expose internal implementation details to users?▼

No, the changelog writing process explicitly hides implementation details. It extracts metadata from PRs or requirement GUIDs and translates them into concise summaries that communicate what changed without exposing internal technical logic.

How do I compile multiple PRs into a single release note?▼

To compile multiple PRs into a single release note, provide several pull request IDs. The skill extracts metadata from each, verifies their merge status, and assembles a combined changelog entry with a unified title, date, and description.

What information do I need to provide to create a brief changelog entry?▼

To create a brief changelog entry, you need to provide either pull request IDs or product requirement document files. The system uses these inputs to extract metadata, verify merge dates, and assemble the final title and description.