skills.rest
JeremyKuhne
JeremyKuhneCOMMUNITY
Explore all skills by this author →
GitHub

publish-release

Guide version bumps, tag selection, and GitHub release creation for Touki releases.

9|1|Updated Jun 6, 2025
Search Tags:#workflow#versioning#release#semver#nuget#tagging#github-release
One-click install
npx skills add https://github.com/JeremyKuhne/touki --skill publish-release-jeremykuhne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-release
Source: https://github.com/JeremyKuhne/touki/tree/main/.agents/skills/publish-release
Command: npx skills add https://github.com/JeremyKuhne/touki --skill publish-release-jeremykuhne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through releasing Touki packages by selecting the correct version bump, prerelease channel, and tag stream, and by publishing a GitHub release after tagging.

Core Features & Use Cases

  • Determine prior version and channel; decide prerelease stage (alpha/beta/rc/stable) and whether to stay on a prerelease or move to stable.
  • Validate and construct the correct SemVer tag formats for both main and TestSupport streams, and initiate the corresponding release workflow.
  • Create and publish the GitHub release notes, coordinating with NuGet packaging and MinVer tagging to ensure consistent artifact versions.

Quick Start

Start the publish-release skill and follow its prompts to tag a new version and publish the corresponding GitHub release.

Frequently Asked Questions about publish-release

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

FAQPage Schema
How do I automate NuGet package versioning and GitHub release tagging for SemVer workflows?▼

Automating NuGet package versioning and GitHub release tagging is handled by guiding SemVer version bumps, validating prerelease tag formats, and coordinating MinVer to publish consistent GitHub releases.

What is the correct SemVer tag format for publishing alpha, beta, and rc prerelease channels?▼

The correct SemVer tag format for prerelease channels requires validating and constructing specific alpha, beta, or rc suffixes across both v* and ts-v* tag streams to initiate proper release workflows.

How do I move a prerelease version to a stable release without breaking AssemblyVersion compatibility?▼

Moving a prerelease version to stable requires selecting the stable channel during the version bump process and evaluating AssemblyVersion considerations to ensure binary changes maintain compatibility.

Does this guided release workflow support separate tag streams for main packages and TestSupport libraries?▼

This guided release workflow supports separate tag streams by validating and constructing both v* tags for the main package and ts-v* tags for the Touki.TestSupport library.

When do I need to bump the major version number versus the minor version for a new GitHub release?▼

You bump the major version number versus the minor version by following enforced versioning rules applied during the guided release preparation to determine the correct SemVer increment.

What are the limitations of using MinVer tagging for NuGet releases in a continuous integration pipeline?▼

Limitations of using MinVer tagging involve coordinating tag creation with NuGet packaging and GitHub release notes to ensure artifact versions remain consistent across both main and TestSupport streams.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1.3k

release-dry-run

Summarize commits and file changes since the latest release tag.

Community
Intermediate
oogDZoogDZ

post-release

Validate GitHub Release notes, CHANGELOG updates, and deployment statuses after publication.

Community
Intermediate
chanhee-kangchanhee-kang
2

auto-deploy

Automate oh-my-gemini deployment to npm and GitHub releases.

Community
Advanced
fabis94fabis94
1

release

Generate a changelog, create a git tag, and publish a GitHub release.

Community
Advanced