What problem does it solve?
Publishing a release involves version selection, release notes, validation gates, tagging, and GitHub Release creation, and mistakes in any step can leave a broken or misleading public release. This Skill enforces an evidence-based checklist so every release is reproducible, verified, and published only after explicit approval.
Core Features & Use Cases
- Evidence-Based Release Preparation: Inspects commits, tags, manifests, and repository policy to determine the correct version, tag shape, and release scope instead of guessing conventions.
- Structured Release Notes: Groups changes by user outcome, documents breaking changes with migration steps, and verifies install commands against current documentation.
- Gated Publication Workflow: Runs repository release gates, presents the exact tag, notes, and validation evidence, and waits for explicit user approval before tagging or publishing.
- Use Case: A maintainer asks to release version 2.1 of a plugin. The Skill reviews commits since the last tag, drafts notes in the repository's house style, runs validation from a clean checkout, presents the full proposal, and only after approval creates the annotated tag and GitHub Release.
Quick Start
Ask the assistant to prepare and publish a new GitHub release for this repository using the release publisher workflow.