release-notes

Name: release-notes
Availability: InStock
Author: weaties

Draft a curated RELEASES.md entry from main branch commits since the last stage/* tag.

2|2|Updated Feb 21, 2026

Search Tags:#automation #git #changelog #documentation #release notes #commit analysis

Ready to run

npx skills add https://github.com/weaties/helmlog --skill release-notes-weaties

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/weaties/helmlog/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/weaties/helmlog --skill release-notes-weaties

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of release notes by summarizing code changes made since the last deployment tag, saving developers time and ensuring consistent documentation.

Core Features & Use Cases

Commit Range Identification: Automatically determines the relevant commit history for release notes.
Change Filtering: Excludes commits that only update ideation logs, focusing on actual code changes.
Thematic Grouping: Organizes changes into logical themes for better readability.
Use Case: Before releasing a new version of your software, run this skill to generate a draft of the RELEASES.md file, detailing all new features, improvements, and bug fixes in a structured format.

Quick Start

Draft a new RELEASES.md entry summarizing commits on main since the latest stage/* tag.

Frequently Asked Questions about release-notes

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

FAQPage Schema

How do I automatically generate release notes from git commits?▼

Generate release notes by analyzing commits on the main branch since the last stage/* tag, filtering out ideation-log-only commits, and grouping remaining changes into logical themes for a structured RELEASES.md entry.

What's the best way to draft a changelog from commit history before a release?▼

Drafting a changelog from commit history involves identifying the commit range since the last deployment tag, excluding non-code updates like ideation logs, and organizing actual code changes into thematic groups for better readability.

Does automated release note generation work with existing stage/* tags in Git?▼

Automated release note generation works with existing stage/* tags in Git by using them as reference points to automatically determine the relevant commit history range for the current release cycle.

How are code changes grouped into themes for structured release documentation?▼

Code changes are grouped into themes for structured release documentation by filtering commit history to exclude ideation-log-only updates, then organizing the remaining actual code modifications into logical categories.

Can I exclude ideation log commits from my automated changelog creation?▼

You can exclude ideation log commits from automated changelog creation by applying a change filtering step that identifies and removes commits updating only ideation logs, focusing the output on actual code changes.

Why do my release notes need to follow a specific markdown format?▼

Release notes need to follow a specific markdown format to ensure consistent documentation and structured readability when drafting the RELEASES.md file detailing new features, improvements, and bug fixes.