release-promoter

Create v-prefixed annotated tags and publish GitHub Releases from changelogs.

Updated Apr 24, 2026

Search Tags:#automation #changelog #github #release #ci-cd #tagging #promotion

Ready to run

npx skills add https://github.com/michael-conrad/.opencode --skill release-promoter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-promoter
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/release-promoter
Command: npx skills add https://github.com/michael-conrad/.opencode --skill release-promoter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates annotated tag creation with a v prefix and the publication of GitHub Releases from the changelog after a release PR merges, reducing manual release toil.

Core Features & Use Cases

Tag creation: generate annotated tags (v-prefixed) on the merge commit and push to remote.
Release publication: create GitHub Releases from tags with the changelog body.
Workflow governance: enforce post-merge tagging discipline and promote releases to GitHub.

Quick Start

Use this skill after a release PR merges to tag the release and publish a GitHub Release with the changelog body.

Frequently Asked Questions about release-promoter

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

FAQPage Schema

How do I automate GitHub Release creation after a release PR is merged?▼

GitHub Release publication is handled by generating an annotated v-prefixed tag on the merge commit and creating the release with the changelog body. This enforces post-merge tagging discipline and returns structured results like the release URL.

How does automated release tagging work with changelogs in CI/CD?▼

Automated release tagging with changelogs works by creating an annotated v-prefixed tag on the merge commit and publishing a GitHub Release. The changelog provides the release body, enforcing post-merge discipline via sub-agent routing.

What is the best way to enforce post-merge tagging discipline for release promotion?▼

The best way to enforce post-merge tagging discipline is to use a release promotion skill that triggers sub-agent routing after a PR merges. This guarantees annotated v-prefixed tags are created and GitHub Releases are published consistently.

Do I need to manually create annotated tags before publishing a GitHub Release?▼

No, you do not need to manually create annotated tags. The automation generates the v-prefixed annotated tag directly on the merge commit and handles the GitHub Release publication automatically using the changelog body.

Can I publish GitHub Releases with a changelog body automatically?▼

Yes, you can publish GitHub Releases automatically with the changelog body by running the promotion workflow after a release PR merges. The process creates the release from the generated tag and populates the release notes.

What results should I expect from an automated release promotion workflow?▼

From an automated release promotion workflow, you should expect structured results containing the generated tag name and the published GitHub Release URL. This confirms successful tag creation and release publication.