Handles the full release pipeline for repositories using Makefile automation.

Install

mkdir -p .claude/skills/release-mkoziy && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12594" && unzip -o skill.zip -d .claude/skills/release-mkoziy && rm skill.zip

Installs to .claude/skills/release-mkoziy

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Publish an http-queue release using this repo's make target. Use when asked to cut, publish, or create a release, tag a semver version like 0.1.1, push multi-arch Docker images to GHCR, or create the matching GitHub release notes from the diff log.
248 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Confirm the version is bare semver.
  • Confirm the current branch is `main`.
  • Confirm the working tree is clean.
  • Confirm Docker is authenticated to GHCR.
  • Confirm `gh auth status` succeeds.
  • Run `make release VERSION=<X.Y.Z>` to publish a release.

How it works

The skill validates preconditions, then executes a Makefile target to automate testing, tagging, multi-arch Docker image pushes, and GitHub release note creation.

Inputs & outputs

You give it
semver version (e.g., 0.1.1)
You get back
published release, Docker images, git tag, and GitHub release notes

When to use release

  • Cutting a new software release
  • Publishing Docker images to registry
  • Creating tagged GitHub releases

About this skill

release

When to use

Use this skill for repo releases only. The canonical path is make release VERSION=<X.Y.Z>.

Preconditions

Before running the release:

  1. Confirm the version is bare semver like 0.1.1.
  2. Confirm the current branch is main.
  3. Confirm the working tree is clean. Do not include unrelated local changes in a release.
  4. Confirm Docker is authenticated to GHCR.
  5. Confirm gh auth status succeeds.

If any precondition fails, stop and report the blocker instead of working around it.

Workflow

  1. Inspect current state:
    • git status --short
    • git branch --show-current
    • git tag --sort=-version:refname | head
  2. If the tree is clean and the user has supplied a version, run:
make release VERSION=<X.Y.Z>
  1. Do not manually recreate the release steps unless the Makefile is broken. The Makefile already:
    • runs go test -race ./...
    • validates semver and branch
    • checks local and remote tag collisions
    • builds and pushes multi-arch images to ghcr.io/mkoziy/http-queue
    • creates and pushes the annotated git tag
    • creates the GitHub release with notes from the git diff log

Verification

After a successful release, report:

  • the released version
  • the pushed image tags:
    • ghcr.io/mkoziy/http-queue:<X.Y.Z>
    • ghcr.io/mkoziy/http-queue:latest
  • the git tag name
  • the GitHub release URL if available from command output

Don't

  • Don't release from a dirty worktree.
  • Don't bypass make release with hand-run git, docker, or gh commands unless fixing the release pipeline itself.
  • Don't guess a version. Use the exact version the user requested.

When not to use it

  • When the repository is not `http-queue`.
  • When the user wants to perform manual release steps outside of `make release`.

Limitations

  • The skill is specific to the `http-queue` repository.
  • The skill requires the current branch to be `main`.
  • The skill requires a clean working tree.

How it compares

This skill automates the entire release process for the `http-queue` repository using a predefined Makefile, ensuring consistency and adherence to release standards, unlike manual release procedures.

Compared to similar skills

release side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
release (this skill)02moReviewIntermediate
gcp-cloud-run55moReviewIntermediate
deployment-pipeline-design62moReviewAdvanced
cloudflare-deploy36moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

gcp-cloud-run

aj-geddes

Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.

5107

deployment-pipeline-design

wshobson

Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.

670

cloudflare-deploy

davila7

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

342

github-release-management

ruvnet

Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management

425

deployment-engineer

sickn33

Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.

418

deploying-machine-learning-models

jeremylongshore

Deploy this skill enables AI assistant to deploy machine learning models to production environments. it automates the deployment workflow, implements best practices for serving models, optimizes performance, and handles potential errors. use this skill when th... Use when deploying or managing infrastructure. Trigger with phrases like 'deploy', 'infrastructure', or 'CI/CD'.

110

Search skills

Search the agent skills registry