release-notes

Convert git commits and tickets into user-facing release notes with adjustable tone.

1|Updated Mar 21, 2026

Search Tags:#changelog #release notes #product communication #git commits #tone adjustment #user-facing writing

Ready to run

npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill release-notes-kalilurrahman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/09-product-management/release-notes
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill release-notes-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams produce raw commits, tickets, and changelogs that users cannot understand. This Skill translates technical artifacts into polished, user-facing release notes that explain what changed and why users should care. ## Core Features & Use Cases - Commit Translation: Reads git commits, Jira tickets, or raw notes and rewrites them in user-facing language, grouping related changes into single items. - Tone Control: Supports B2B Formal, B2C Friendly, and Internal tones, defaulting to B2B Formal when unspecified. - Structured Output: Organizes notes into New Features, Improvements, and Bug Fixes, with an optional Internal Notes section for support teams. - Use Case: Paste a sprint's worth of git commits and receive a ready-to-publish changelog file saved as release-notes-[version-or-date].md. ## Quick Start Paste your recent git commits or a file path and ask the assistant to generate user-facing release notes in a B2B formal tone.

Frequently Asked Questions about release-notes

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

FAQPage Schema

How do I turn git commits into release notes?▼

Provide a git repository path or paste commit messages, and the Skill extracts changes using git log, groups related commits, and rewrites each item in user-facing language organized by features, improvements, and fixes.

How to write release notes for non-technical users?▼

Translate every technical change into user impact, describing what users will notice rather than how it was built. For example, a null pointer fix becomes a resolved login issue, and internal refactors with no user impact are omitted.

Can release notes have different tones for different audiences?▼

Yes, the Skill supports three tones: B2B Formal for enterprise changelogs, B2C Friendly for consumer apps, and Internal for team updates with ticket references. If no tone is specified, it defaults to B2B Formal.

Should internal refactors appear in user-facing release notes?▼

No, internal refactors with zero user impact should be omitted from user-facing sections. They can be moved to an optional Internal Notes section intended for support teams, CSMs, or internal stakeholders.

Where are the generated release notes saved?▼

The output is written to a Markdown file named release-notes-[version-or-date].md in the current working directory, containing the release title, version, date, and categorized change sections.