mkl-prepare-release
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.
Install
npx skills add https://github.com/00200200/maintainer-skills-lab/tree/main/providers/codex/.agents/skills/mkl-prepare-release
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install 00200200-maintainer-skills-lab@llmmart
git clone https://github.com/00200200/maintainer-skills-lab.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole 00200200/maintainer-skills-lab collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
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.
Files (maintainer-skills-lab)
-
SKILL.md 1.5 KB
--- 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.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.