ABOUTME: Release preparation skill with pre-flight verification, prevents retag-four-times pattern

ABOUTME: Invoked on "release", "tag", "ship it", "push to production"

Releasing Software

Rule

Tag only after CI is green on the release commit. Run full verification locally, fix everything, then tag: a tag cut before CI passes gets deleted and recut when CI fails, and every retag breaks whoever already pulled it.

Pre-Release Checklist

Release Procedure

Only after ALL checks pass:

1. Commit: git add -A && git commit -m "release: prepare vX.Y.Z"
2. Wait for pre-commit hooks
3. Push and WAIT: git push origin main
4. Check CI: gh run list --limit 2
5. Only after green: git tag -a vX.Y.Z -m "vX.Y.Z" && git push origin vX.Y.Z
6. Verify release workflow triggered

Stop and reassess if you catch yourself

• Tagging before CI completes
• "CI will probably pass"
• Deleting/recreating tags
• Force-pushing tags

Common Failures

Troubleshooting

# Verify goreleaser config
goreleaser check

# Dry run release
goreleaser release --snapshot --clean

# Check for packages without tests
find . -type d -not -path "*/.*" -exec sh -c 'ls {}/*_test.go 2>/dev/null || echo "No tests: {}"' \;