github:release

Publish draft GitHub releases after verifying CI on main.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/fabn/claude-plugins --skill github-release-fabn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github:release
Source: https://github.com/fabn/claude-plugins/tree/main/plugins/github/skills/release
Command: npx skills add https://github.com/fabn/claude-plugins --skill github-release-fabn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help release managers and developers publish draft releases created by Release Drafter by locating the appropriate draft, validating CI on main, and safely promoting the draft to a published release while preventing accidental or unsafe publishes.

Core Features & Use Cases

  • Locate Draft Releases: List and detect draft releases in the repository and present choices when multiple drafts exist.
  • CI Validation: Inspect recent workflow runs on the main branch, wait for in-progress runs, and stop on failing builds to avoid publishing broken releases.
  • Safe Publishing Workflow: Require explicit user confirmation before publishing, perform the publish via the gh CLI, and verify the release is no longer marked as a draft.
  • Error Handling & Guidance: Provide clear guidance when prerequisites are missing (gh CLI, auth), when no drafts exist, or when publishing fails due to permissions.

Quick Start

Run the github:release skill to find the latest draft release, verify CI on main, confirm with you, and publish the selected draft.

Frequently Asked Questions about github:release

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

FAQPage Schema
How do I safely publish a draft GitHub release created by Release Drafter?

To safely publish a draft GitHub release, the workflow locates the appropriate draft, validates CI status on the main branch, presents a changelog preview, and requires explicit confirmation before promoting it to a live release.

What happens if there are multiple draft releases in my repository?

When multiple draft releases exist in the repository, the workflow lists and detects all available drafts, presenting you with choices to select the correct candidate before proceeding with any publishing actions.

Do I need the gh CLI installed to publish draft releases?

Yes, you need the gh CLI installed and properly authenticated, as the workflow uses it to perform the publish operation and verifies proper GitHub authentication and permissions are configured before proceeding.

How does CI validation work before publishing a GitHub release?

CI validation inspects recent workflow runs on the main branch, waits for any in-progress runs to complete, and halts the publishing process if builds are failing to prevent publishing broken releases.

What errors might I encounter when publishing a GitHub release?

Common errors include missing prerequisites like the gh CLI or authentication, no draft releases existing in the repository, or publishing failures due to insufficient GitHub permissions, all providing clear guidance.

Can I use GitHub MCP tooling instead of the gh CLI to publish releases?

Yes, the workflow supports publishing draft releases using either the gh CLI or GitHub MCP tooling, provided proper authentication and permissions are configured for the chosen method.