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 you need to publish a new version of a Go project that uses GoReleaser for automated builds and releases.
For projects that do not use GoReleaser or require a different release workflow (e.g., manual uploads, other CI triggers).
Security analysis
SafeThe 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
Release a new patch version with the message 'Fix homebrew cask configuration' to trigger GoReleaser.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
-
Check current state
- Run
git statusto ensure working directory is clean - If there are uncommitted changes, stop and ask the user to commit first
- Run
-
Get the latest tag
- Run
git tag -l --sort=-v:refname | head -1to get the current version - Current versioning follows semver:
v0.0.X
- Run
-
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)
-
Gather release notes
- Run
git log $(git describe --tags --abbrev=0)..HEAD --onelineto see commits since last tag - Summarize the changes for the tag message
- Run
-
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
- Create annotated tag:
-
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
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.