release-notes

Name: release-notes
Availability: InStock
Author: Sir-chawakorn

Generate changelogs from git history using Conventional Commit standards.

9|3|Updated Jun 13, 2026

Search Tags:#automation #git #changelog #documentation #release #conventional-commits

Ready to run

npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill release-notes-sir-chawakorn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/release-notes
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill release-notes-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of turning raw, technical git commit history into clean, professional, and user-friendly release notes that highlight actual value rather than implementation details.

Core Features & Use Cases

Automated Summarization: Converts Conventional Commits into categorized sections like Added, Fixed, and Security.
Noise Reduction: Automatically filters out internal noise like chore, test, and build commits to focus on user-facing changes.
Breaking Change Detection: Identifies and highlights breaking changes to ensure users are warned about migration requirements.

Quick Start

Ask the assistant to generate release notes for the range between the latest tag and the current head of the repository.

Frequently Asked Questions about release-notes

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

FAQPage Schema

How do I generate human-readable changelogs from git commit history?▼

To generate human-readable changelogs from git commit history, this skill parses commit subjects and bodies, applying Conventional Commit standards to group changes into structured Keep-a-Changelog sections.

Does generating release notes with Conventional Commits filter out internal build and test commits?▼

Yes, generating release notes with Conventional Commits automatically filters out internal noise like chore, test, and build commits to focus on user-facing changes rather than implementation details.

How are breaking changes detected when creating changelogs from git history?▼

Breaking changes are detected when creating changelogs by parsing git commit subjects and bodies for specific breaking change indicators, highlighting them to warn users about migration requirements.

What is the best way to document version changes between the latest git tag and the current head?▼

The best way to document version changes between the latest git tag and the current head is to parse that specific commit range and categorize the extracted changes into structured Added, Fixed, and Security sections.

Do I need Conventional Commit standards to generate Keep-a-Changelog sections from git?▼

Yes, Conventional Commit standards are required to generate Keep-a-Changelog sections, as the skill relies on these commit message conventions to accurately categorize changes and reduce internal noise.

What limitations exist when parsing git commit bodies for release notes?▼

A key limitation when parsing git commit bodies for release notes is that the skill requires strict adherence to Conventional Commit standards to correctly detect breaking changes and filter out internal noise.