release-notes-synthesizer

Convert commit histories into Markdown release notes from Conventional Commits and PR descriptions.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/DaFum/neurotoxic-game --skill release-notes-synthesizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes-synthesizer
Source: https://github.com/DaFum/neurotoxic-game/tree/main/.agents/skills/release-notes-synthesizer
Command: npx skills add https://github.com/DaFum/neurotoxic-game --skill release-notes-synthesizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting chaotic commit histories into clear, publish-ready release notes to save time and ensure consistency across releases.

Core Features & Use Cases

  • Conventional Commit parsing: categorizes commits into Features, Fixes, and Refactors; identifies breaking changes.
  • Changelog generation: compiles a structured Markdown release notes document including known issues and dependency updates.
  • PR and commit summaries: integrates PR descriptions and commit messages to produce a cohesive narrative for stakeholders.
  • Use Case: Imagine preparing notes for a new release where dozens of commits describe features and bug fixes; this skill summarizes them into a readable changelog.

Quick Start

Draft a release notes section from the latest commits and PR summaries.

Frequently Asked Questions about release-notes-synthesizer

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

FAQPage Schema
How do I generate release notes from conventional commits?

Generate release notes from conventional commits by parsing prefixes to categorize features, fixes, and refactors, then compiling them into a structured Markdown changelog. This process summarizes chaotic commit histories into a readable narrative for stakeholders.

What is the best way to turn git commit histories into a Markdown changelog?

Turning git commit histories into a Markdown changelog involves identifying breaking changes and dependency updates from commit messages and PR descriptions. This categorization creates a cohesive, publish-ready release notes document without manual sorting.

Can I use PR descriptions to create structured release notes?

PR descriptions can be used to create structured release notes by integrating them with commit summaries. This combines the high-level context from pull requests with detailed conventional commit histories to produce a comprehensive changelog.

How does conventional commit parsing identify breaking changes for release notes?

Conventional commit parsing identifies breaking changes by analyzing commit prefixes and metadata. It flags these changes specifically so they can be highlighted in the generated Markdown release notes, ensuring stakeholders are aware of critical updates.

Do I need a specific commit message format to automate changelog generation?

Automating changelog generation requires a structured commit message format like conventional commits. Parsing these prefixes allows the system to accurately categorize features, fixes, and refactors into a well-structured Markdown document.

How to compile dependency updates and known issues into release notes?

Compile dependency updates and known issues into release notes by parsing commit histories and PR summaries. The process extracts these specific details and lists them in a dedicated section within the generated Markdown changelog.