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.

Sby Skills Guide Bot
DevOpsIntermediate
806/2/2026
Claude Code
#release#git-tag#goreleaser#versioning

Recommended for

Our review

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

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
Related skills