write-changelog

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.

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.

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.

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.

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.

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.