mcpbeat

Release Notes

microsoft/release-notes

Generate release notes from commit history. Use when asked to draft release notes, create a changelog, or summarize changes for a release.

447 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
82
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/microsoft/intelligent-terminal --skill release-notes

The instruction itself

5 sections, as written by the author

Release Notes

Overview

A structured process for generating release notes from commit history. Groups changes by type, highlights breaking changes, and produces user-friendly summaries.

Patterns & Techniques

Generation Process

Step 1: Gather changes

git log --oneline $(git describe --tags --abbrev=0)..HEAD

Step 2: Categorize using conventional commit prefixes:

  • 🚀 Features (feat:)
  • 🐛 Bug Fixes (fix:)
  • 📚 Documentation (docs:)
  • 🔧 Maintenance (chore:, refactor:)
  • ⚠️ Breaking Changes (BREAKING CHANGE or !)

Step 3: Write using the template:

# Release vX.Y.Z

## Highlights
Brief summary of the most important changes (2-3 sentences).

## 🚀 Features
- Description of feature (#PR)

## 🐛 Bug Fixes
- Description of fix (#PR)

## ⚠️ Breaking Changes
- What changed and migration steps

## 📚 Documentation
- What was updated

## 🔧 Maintenance
- Internal changes

Step 4: Review

  • All significant changes included
  • PR/issue references correct
  • Breaking changes include migration instructions

Common Pitfalls

  • Listing commit messages verbatim — Rewrite for the reader, not the committer
  • Missing breaking changes — Always call these out prominently with migration steps
  • No highlights section — Users want a 2-sentence summary, not a raw list

How to use it

Copy the folder

Take microsoft/release-notes from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.