goreleaser-release-pipeline
Installation
SKILL.md
GoReleaser release pipeline
Use this skill when a repository already has, or is adding, a GoReleaser v2 release flow and the important question is how Release Please, tags, GitHub releases, and publish jobs fit together without losing versioned releases or assets.
Use this skill when
- You are wiring Release Please to a GoReleaser v2 publish flow.
- A release is created, but the GitHub release has no binary assets.
- A GoReleaser publish job fails because the tag is not plain semver.
- You need to fix tag shape, publish-job conditions, or Release Please outputs without redesigning the whole CI system.
- The team cares about preserving release numbers for downstream monitoring or release correlation.
Do not use this skill when
- The main task is generic GitHub Actions runner, cache, permission, or environment triage with no release-pipeline-specific evidence.
- The main task is deciding how to merge, keep, or discard a finished branch.
- The main task is creating, updating, or managing a pull request.
- The repository is not using GoReleaser or Release Please.