skills.rest
mifunedev
mifunedevOFFICIAL
Explore all skills by this author →
Website𝕏@mifunedevGitHub

release

Automate CalVer release workflows with version computation, pre-flight checks, and artifact publishing.

28|3|Updated Mar 27, 2026
Search Tags:#git#versioning#release#github-actions#ci#calver
One-click install
npx skills add https://github.com/mifunedev/openharness --skill release-mifunedev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mifunedev/openharness/tree/main/.claude/skills/release
Command: npx skills add https://github.com/mifunedev/openharness --skill release-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CalVer-based release workflows often require manual coordination of versioning, branch creation, and artifact publishing. This Skill automates the end-to-end release process to reduce errors and save time.

Core Features & Use Cases

  • Auto-derive a CalVer version from the current date and existing tags.
  • Create and push the release branch, tag, and associated CHANGELOG updates.
  • Poll CI and verify release artifacts (GitHub Release and GHCR images) post-build.
  • Use-case: release a new version after a feature complete, with pre-flight checks to ensure repository health.

Quick Start

Run the release skill on the target repository to automatically compute the version, create the release branch and tag, poll CI, and verify artifacts.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a CalVer release workflow with GitHub Actions?▼

You can automate a CalVer release workflow by running this skill to compute versions from dates and existing tags, create release branches, push tags, and poll GitHub Actions CI to verify artifacts.

How does CalVer version derivation from git tags work?▼

CalVer version derivation computes the release version using the current date combined with existing git tags, ensuring chronological versioning without manual numbering decisions.

Can I publish GitHub Release and GHCR images automatically after a CI build?▼

Yes, the skill polls CI after pushing the release tag and verifies that both the GitHub Release and GHCR images are published as expected artifacts.

What pre-flight checks are needed before creating a release branch and tag?▼

Pre-flight checks verify repository health by ensuring the Unreleased section in the CHANGELOG is populated and git remotes are properly configured before creating the release branch and tag.

What is the best way to manage release branches and tags for calendar versioning?▼

Automating the process with a dedicated skill ensures the release branch and tag are created and pushed consistently based on the derived CalVer version, reducing manual coordination errors.

What happens if the CHANGELOG Unreleased section is empty during a release?▼

The pre-flight checks read the CHANGELOG to ensure the Unreleased section contains updates, preventing incomplete releases from proceeding without documented changes.

Related Skills

Explore More Software Engineering Skills→
usetheodevusetheodev

release

Orchestrate semantic releases from develop to main with approval gates.

Community
Advanced
rudironsonirudironsoni

dotnet-gha-publish

Automate .NET artifact publishing in GitHub Actions workflows.

Community
Advanced
aapw01aapw01

Git Workflow & CI/CD

Implement Git workflow best practices and automate CI/CD pipelines with GitHub Actions.

Community
Advanced
kabakakabaka

calver-release

Schedule and enforce CalVer releases with automated changelog and git tag updates.

Community
Intermediate