skills.rest
heaptracetechnology
heaptracetechnologyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release-notes

Extract git commits between two points and generate categorized client-facing release notes.

13|3|Updated Mar 27, 2026
Search Tags:#automation#git#changelog#documentation#release-notes#client-facing
One-click install
npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill release-notes-heaptracetechnology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/heaptracetechnology/heaptrace-skills/tree/main/release-notes
Command: npx skills add https://github.com/heaptracetechnology/heaptrace-skills --skill release-notes-heaptracetechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill parses git history between two points and converts it into clear, client-friendly release notes, saving time and reducing confusion for stakeholders.

Core Features & Use Cases

  • Reads commits and tags between two release points and groups changes by category (features, fixes, improvements, breaking changes).
  • Produces client-facing narratives suitable for release notes, internal changelogs, and customer communications.
  • Use Case: Before a release, generate a concise changelog that highlights new capabilities, bug fixes, and any migration steps.

Quick Start

Specify the two git points (tags, branches, or dates) to compare and run the skill to generate release notes.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I generate client-facing release notes from git history?▼

Yes, you can group git commits by category for changelogs. The skill extracts commits between two specified points and categorizes them into features, fixes, improvements, and breaking changes, producing structured narratives suitable for internal changelogs and external customer communications.

How do I translate technical git commits into plain language for stakeholders?▼

To translate technical git commits into plain language, the skill parses commit history between two release points and automatically converts technical details into clear, client-friendly narratives, reducing confusion and saving time for stakeholders reviewing the changes.

Can I use this for sprint demos and internal changelogs?▼

Yes, you can use this for sprint demos and internal changelogs. The generated release notes are applicable to releases, sprint demos, and client communications, producing clear narratives that highlight new capabilities, bug fixes, and any necessary migration steps.

What is the best way to automate changelog creation from git commits?▼

The best way to automate changelog creation from git commits is specifying two release points for comparison. The automation collects the commits, categorizes changes by type, translates technical details into plain language, and formats the results for delivery.

Related Skills

Explore More Content & Communication Skills→
wgpsecwgpsec
1.6k

githacker-git-leak

Recover full source code from exposed remote Git .git directories.

Official
Advanced
product-on-purposeproduct-on-purpose
527

deliver-release-notes

Generate user-facing release notes from changelog data.

Official
Basic
imclabimclab
1

changelog

Generate internal and player-facing changelogs from git commits and sprint reports.

Official
Intermediate
MichaelSolatiMichaelSolati

changelog

Generate categorized internal and player-facing changelogs from git history and sprint reports.

Community
Advanced