release-notes

Convert Git commits into jargon-free HTML release notes categorized by user impact.

9|2|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/atournayre/claude-marketplace --skill release-notes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/atournayre/claude-marketplace/tree/main/git/skills/release-notes
Command: npx skills add https://github.com/atournayre/claude-marketplace --skill release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the time-consuming process of manually translating technical commit messages into clear, user-focused release documentation that anyone can understand.

Core Features & Use Cases

  • Automated Translation: Converts developer commit messages into plain language without technical jargon.
  • Smart Categorization: Automatically groups changes into New Features, Improvements, Fixes, and Security updates.
  • Professional HTML Output: Generates beautifully formatted release notes with responsive design.
  • Use Case: After completing a development sprint with 50+ commits, use this Skill to automatically create polished release notes that clearly communicate what's new to your users.

Quick Start

Use the release-notes skill to generate user-friendly release notes comparing the main branch with the latest development branch.

Frequently Asked Questions about release-notes

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

FAQPage Schema
How do I convert Git commits into user-friendly release notes?

Convert Git commits into user-friendly release notes by collecting commits between branches, categorizing them by user impact (features, improvements, fixes, security), removing technical jargon, and generating formatted HTML output. The Skill automates this translation end-to-end, storing results in .claude/reports/.

Can I automatically categorize commits into features, fixes, and improvements?

Yes, the Skill automatically categorizes commits into New Features, Improvements, Fixes, and Security updates based on user impact rather than technical detail. It filters out non-user-visible changes to focus only on what matters to end users.

What's the best way to generate release notes from a development branch?

Compare your development branch against main using this Skill to generate professional HTML release notes. Specify source and target branches, and it collects all commits, rewrites them in plain language, and produces a formatted report automatically.

Does this work for release workflows with multiple commits?

Yes, this Skill scales to high-volume workflows. After a sprint with 50+ commits, it processes the entire set, groups them by impact category, and generates a single polished HTML release document that communicates changes clearly to users.

Can I customize which branches to compare for release notes?

Yes, the Skill accepts argument parsing for source and target branch specification, with an optional default release branch. Configure which branches to compare, and it automatically collects and translates commits between them.

What happens to technical jargon in commit messages?

The Skill rewrites technical commit messages in jargon-free language so non-technical stakeholders understand the changes. It removes developer-specific terminology while preserving the user-facing meaning of each commit.