publish-release

Regenerate GitHub release drafts with current PRs and impact assessments.

4.5k|777|Updated Mar 10, 2025

Search Tags:#automation #github #release #release notes #pr #draft

Ready to run

npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill publish-release-modelcontextprotocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: publish-release
Source: https://github.com/modelcontextprotocol/csharp-sdk/tree/main/.github/skills/publish-release
Command: npx skills add https://github.com/modelcontextprotocol/csharp-sdk --skill publish-release-modelcontextprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually creating and updating release notes for GitHub projects can be time-consuming and error-prone, especially when tracking multiple PRs and updates across versions.

Core Features & Use Cases

Automated Release Drafts: Generate draft releases with up-to-date release notes reflecting recent merged PRs.
Release Notes Refresh: Recalculate and include new PRs merged after release prep, alerting about potential breaking changes.
Use Case: When preparing a new software version, quickly assemble accurate release notes and a draft release on GitHub for review before publishing.

Quick Start

Provide the PR number or version, and this Skill will identify the prepare-release PR, analyze the merge range, refresh release notes, and create a draft release for review.

Frequently Asked Questions about publish-release

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

FAQPage Schema

How do I automate GitHub release notes creation from merged PRs?▼

Automate GitHub release notes by providing a PR number or version to regenerate release drafts. The Skill analyzes the merge range, includes recent PRs, and creates a draft release on GitHub for review before publishing.

Can I refresh GitHub release drafts after new PRs are merged?▼

Yes, you can refresh GitHub release drafts to recalculate and include new PRs merged after release prep. The update alerts you about potential breaking changes to ensure accurate tracking before publishing.

Do I need GitHub CLI access to generate automated release drafts?▼

Yes, generating automated release drafts requires access to GitHub CLI, your repository, and PR data. This access ensures accurate tracking of merged PRs and potential impact assessments for your release notes.

What is the best way to track breaking changes when preparing a GitHub release?▼

The best way to track breaking changes is to refresh release notes during preparation. The Skill recalculates the merge range and warns about potential breaking impacts from newly merged PRs before you publish the draft.

How do I create a GitHub draft release for continuous deployment workflows?▼

Create a GitHub draft release for continuous deployment by providing a version or PR number. The Skill identifies the prepare-release PR, analyzes the merge range, and assembles a draft with accurate notes for review.