Skills Guide

Release and Version Management

VerifiedSafe

Creates and pushes annotated version tags (semver) to trigger the GoReleaser CI pipeline. It checks git status, determines the next version via patch/minor/major bump, and generates release notes from commit history. Helps when releasing new versions of a Go project.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
6/2/2026
Claude Code
#release#git-tag#goreleaser#versioning

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Automated summary

Creates a new version tag with a release message and pushes it to trigger the GoReleaser CI pipeline.

Strengths

  • Automates semantic versioning bump (patch/minor/major)
  • Generates release notes from recent commit history
  • Verifies clean working directory before tagging
  • Pushes only the tag, not the branch

Limitations

  • Requires a clean git working tree with no uncommitted changes
  • Assumes a specific tag naming convention (v0.0.X)
  • Does not support pre-release suffixes (e.g., -alpha)
When to use it

When you need to publish a new version of a Go project that uses GoReleaser for automated builds and releases.

When not to use it

For projects that do not use GoReleaser or require a different release workflow (e.g., manual uploads, other CI triggers).

Security analysis

Safe
Quality score90/100

The skill uses standard git commands for tagging and pushing, with no destructive, exfiltrating, or obfuscated actions. All operations are confined to version control within the repository.

No concerns found

How this analysis is made

Examples

Patch release for bug fix
Release a new patch version with the message 'Fix homebrew cask configuration' to trigger GoReleaser.
Minor release with multiple changes
Create a new minor version tag for the project with release notes summarizing recent commits, then push it.

name: release description: Create a new version tag with release message and push to trigger GoReleaser. Use when user wants to release, tag, bump version, or publish a new version. allowed-tools: Bash, Read, Grep

Release

Create and push a new version tag to trigger the GoReleaser CI pipeline.

Instructions

  1. Check current state

    • Run git status to ensure working directory is clean
    • If there are uncommitted changes, stop and ask the user to commit first

  2. Get the latest tag

    • Run git tag -l --sort=-v:refname | head -1 to get the current version
    • Current versioning follows semver: v0.0.X

  3. Determine next version

    • Ask the user what type of bump they want (patch/minor/major) or if they want a specific version
    • Default to patch bump (e.g., v0.0.5 -> v0.0.6)

  4. Gather release notes

    • Run git log $(git describe --tags --abbrev=0)..HEAD --oneline to see commits since last tag
    • Summarize the changes for the tag message

  5. Create and push the tag

    • Create annotated tag: git tag -a vX.Y.Z -m "Release message"
    • Push the tag: git push origin vX.Y.Z

  6. Confirm success

    • Provide the GitHub releases URL: https://github.com/lch88/logbro/releases

Tag Message Format

Use a concise summary of changes. Examples:

  • Single change: Fix homebrew cask configuration
  • Multiple changes: Add dark mode support, fix memory leak, improve performance

Example

# Check status
git status

# Get current version
git tag -l --sort=-v:refname | head -1
# Output: v0.0.5

# See changes since last tag
git log v0.0.5..HEAD --oneline

# Create tag
git tag -a v0.0.6 -m "Move main.go to cmd package, update goreleaser config"

# Push tag
git push origin v0.0.6

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/release-and-version-management-mm78nnvg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/release-and-version-management-mm78nnvg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/release-and-version-management-mm78nnvg/download' --output '.skill-downloads/release-and-version-management-mm78nnvg/SKILL.md.part' && mv '.skill-downloads/release-and-version-management-mm78nnvg/SKILL.md.part' '.skill-downloads/release-and-version-management-mm78nnvg/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/release-and-version-management-mm78nnvg/SKILL.md' && test -s '.skill-downloads/release-and-version-management-mm78nnvg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/release' && cp -R '.skill-downloads/release-and-version-management-mm78nnvg' '.claude/skills/release'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/release-and-version-management-mm78nnvg'

openskills read 'release-and-version-management-mm78nnvg'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/release-and-version-management-mm78nnvg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot