release-notes

Generate Markdown release notes from merged PRs between version tags.

16|6|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/kagenti/adk --skill release-notes-kagenti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-notes
Source: https://github.com/kagenti/adk/tree/main/.claude/skills/release-notes
Command: npx skills add https://github.com/kagenti/adk --skill release-notes-kagenti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) components.

What problem does it solve?

Manually creating release notes for software versions is time-consuming and error-prone; this skill automates the production of user-focused notes that summarize changes, impact, and deployment details for each version.

Core Features & Use Cases

  • Scope-aware notes: derives content from merged PRs between a start version and an end version to produce a coherent release narrative.
  • User-focused summaries: emphasizes outcomes and practical impact for end users, admins, and developers.
  • Multi-channel ready: formats notes suitable for GitHub release pages and Slack announcements.

Quick Start

Provide a release tag like release-v0.5.0 to generate user-focused 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 user-friendly release notes from merged PRs in GitHub?

Generate user-friendly release notes by comparing merged PRs between a start version and an end version tag. This process transforms GitHub commit history into a concise, Markdown-ready summary suitable for release pages.

Can I format automated release notes for Slack announcements?

Yes, automated release notes can be formatted for Slack announcements. The generated summaries are multi-channel ready, producing user-focused Markdown content suitable for both GitHub release pages and Slack.

Do I need git and gh installed to automate version tag release notes?

Yes, you need git and gh installed to automate version tag release notes. These dependencies are required to identify the start commit from the latest stable version and compare history to the end tag.

What is the best way to summarize GitHub PR merges for a new version tag?

The best way to summarize GitHub PR merges is scope-aware automation. It derives content from merged PRs between a start and end version to produce a coherent narrative emphasizing outcomes and practical impact.

How does identifying the start commit from the latest stable version work for release notes?

Identifying the start commit from the latest stable version works by comparing git history to a specified end tag. This scope-aware mechanism captures all relevant merged PRs to build a coherent release narrative.

When do I need to use an automated release notes generator?

You need an automated release notes generator when manually creating software version summaries becomes time-consuming and error-prone. It automates the production of user-focused notes detailing changes, impact, and deployment information.