Prepare release notes and migration guidance from a verified revision range and project release policy. Use for release preparation; never present open PRs or planned changes as shipped features.
Installs into .claude/skills of the current project.
Are you the author of Mkl Prepare Release?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/00200200-mkl-prepare-release)
---
name: "mkl-prepare-release"
description: "Prepare release notes and migration guidance from a verified revision range and project release policy. Use for release preparation; never present open PRs or planned changes as shipped features."
---
# Prepare a release
Read the project's release policy, previous release, and requested target revision. Resolve the revision range before summarizing. Keep unmerged work and future plans separate from changes actually included in that range.
Group changes by their effect on users: additions, fixes, behavior changes, deprecations, and removals. Link claims to commits, PRs, or affected public interfaces. Omit internal churn that has no useful consequence for the reader.
For breaking changes, show the previous and new behavior and a concrete migration example. Inspect package metadata, supported runtimes, installation instructions, and required release checks. Treat CI badges and old test output as insufficient evidence for the current revision.
Return draft release notes, a migration section when needed, the evaluated revision range, completed checks, and remaining release blockers. Follow the repository's versioning policy; don't invent a version if the user's requested release is still ambiguous.
Creating tags, publishing packages or releases, and sending announcements are separate external actions. Perform them when already authorized by the user; otherwise finish the reviewable draft and identify the exact remaining action.
