skills.rest
chavangorakh1999
chavangorakh1999COMMUNITY
Explore all skills by this author →
Website𝕏@grc_jrGitHub

release-notes

Generate categorized Markdown changelogs from commit lists or PR titles.

1|Updated Mar 6, 2026
Search Tags:#git#changelog#developer tools#documentation#conventional commits#release notes
One-click install
npx skills add https://github.com/chavangorakh1999/sde-skills --skill release-notes-chavangorakh1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/chavangorakh1999/sde-skills/tree/main/sde-execution/skills/release-notes
Command: npx skills add https://github.com/chavangorakh1999/sde-skills --skill release-notes-chavangorakh1999

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of professional, user-facing release notes by transforming raw commit messages or PR titles into a structured, categorized changelog.

Core Features & Use Cases

  • Categorization: Automatically sorts changes into conventional commit categories (feat, fix, breaking, security, etc.).
  • Formatting: Generates release notes in a clean Markdown format suitable for documentation or release announcements.
  • Use Case: After merging a sprint's worth of commits, use this Skill to quickly generate the release notes for the upcoming software version, ensuring all significant changes are clearly communicated to users.

Quick Start

Use the release-notes skill to generate release notes from the provided commit messages.

Frequently Asked Questions about release-notes

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

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

To generate release notes from conventional commits, this Skill parses raw commit messages or PR titles and automatically categorizes them into structured sections like feat, fix, breaking, and security to produce a clean Markdown changelog.

What is the best way to create a categorized changelog from a list of git commits?▼

Creating a categorized changelog from a list of git commits involves sorting raw commit messages into conventional categories such as feat, fix, breaking, deprecated, and security, which this Skill automates to output structured Markdown documentation.

Can I use PR titles instead of commit messages to generate a developer-facing changelog?▼

Yes, you can use PR titles to generate a developer-facing changelog. This Skill processes either raw commit messages or PR titles, categorizing the provided text into conventional commit sections for your release documentation.

Does this changelog generation approach support categorizing security and deprecated changes?▼

Yes, this changelog generation approach supports categorizing security and deprecated changes. It automatically sorts input commits into predefined sections including feat, fix, breaking, deprecated, and security.

How do I format raw git commit messages into Markdown for release announcements?▼

Formatting raw git commit messages into Markdown for release announcements is done by categorizing commits into conventional sections and generating a clean Markdown document, which this Skill automates from your provided commit list.

Related Skills

Explore More Software Engineering Skills→
lips85lips85

git-commit-formatter

Format Git commit messages according to the Conventional Commits specification.

Community
Basic
hdkz-devhdkz-dev

changeset-management

Manage versioning, changelogs, and release tagging for monorepos using Changesets.

Community
Intermediate
l3ochol3ocho

changelog-format

Parse Conventional Commits and Keep a Changelog formats to generate release notes.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

generate-changelog

Generate markdown changelog entries from git commit messages.

Official
Intermediate