skills.rest
00200200
00200200COMMUNITY
Explore all skills by this author →
GitHub

mkl-prepare-release

Generate release notes and migration guidance from a verified revision range.

11|1|Updated Sep 13, 2026
Search Tags:#git#changelog#versioning#breaking changes#release notes#migration guide#release preparation
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-prepare-release-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-prepare-release
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-prepare-release
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-prepare-release-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes by hand risks mixing unmerged work with shipped changes, missing breaking-change migration steps, and citing stale CI results as evidence. This Skill produces draft release notes grounded in a resolved revision range and the project's own release policy. ## Core Features & Use Cases - Verified Revision Range: Resolves the exact commit range before summarizing, so only changes actually included in the release appear in the notes. - User-Impact Grouping: Organizes changes into additions, fixes, behavior changes, deprecations, and removals, each linked to commits, PRs, or affected public interfaces. - Breaking-Change Migration Guidance: Shows previous versus new behavior with a concrete migration example for every breaking change. - Use Case: Before tagging v2.3.0, ask the Skill to draft release notes from v2.2.0 to HEAD; it returns grouped notes, a migration section, completed checks, and remaining release blockers. ## Quick Start Ask the assistant to prepare draft release notes and migration guidance for the changes between the previous release tag and the current HEAD revision.

Frequently Asked Questions about mkl-prepare-release

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

FAQPage Schema
How do I write release notes from a git revision range?▼

Resolve the exact revision range first, then summarize only the changes merged within it. Group entries by user impact such as additions, fixes, and deprecations, and link each claim to its commit or pull request.

How do I document breaking changes in release notes?▼

Show the previous behavior and the new behavior side by side, then provide a concrete migration example. Inspect package metadata, supported runtimes, and installation instructions so the guidance reflects the current revision.

Should release notes include open pull requests or planned features?▼

No. Open PRs and future plans must stay separate from changes actually included in the evaluated revision range. Presenting unmerged work as shipped features misleads users upgrading to the release.

Can CI badges be used as evidence a release is ready?▼

No. CI badges and old test output are insufficient evidence for the current revision. Run the required release checks against the actual target revision and report completed checks and remaining blockers.

Does this Skill publish the release or create tags?▼

No. Creating tags, publishing packages, and sending announcements are separate external actions. The Skill finishes a reviewable draft and identifies the exact remaining action unless publishing is already authorized.

Related Skills

Explore More Software Engineering Skills→
chenxingqiangchenxingqiang

changelog-scan

Extract titles, labels, and types from merged pull requests and commits via GitHub APIs.

Community
Basic
AllBeingsFutureAllBeingsFuture
9

publish-agent

Package and publish local Agent profiles to the AllBeingsFuture Agent Store.

Community
Intermediate
chrisbaneschrisbanes
1.0k

grounded-writing

Draft and revise evidence-led publishable prose without invented claims or promotional filler.

Community
Intermediate
psengerpsenger
9

git-commit-pr-message

Generate conventional git commit messages, PR titles, and changelog entries from staged changes.

Community
Advanced