goreleaser-setup
Set up goreleaser for Go release automation with cross-compilation and publishing.
npx skills add a5c-ai/babysitter --skill goreleaser-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Goreleaser Setup Set up goreleaser for Go release automation. ## Generated Patterns ```yaml # .goreleaser.yaml version: 2 builds: - env: [CGO_ENABLED=0] goos: [linux, windows, darwin] goarch: [amd64, arm64] ldflags: - -s -w -X main.version={{.Version}} archives: - format: tar.gz format_overrides: - goos: windows format: zip checksum: name_template: 'checksums.txt' changelog: sort: asc filters: exclude: ['^docs:', '^test:', '^chore:'] brews: - repository: owner: myuser name: homebrew-tap homepage: https://github.com/myuser/myapp description: My CLI application ``` ## Target Processes - cli-binary-distribution - package-manager-publishing
- Generated Patterns
- Target Processes
What does the goreleaser-setup skill do?
Set up goreleaser for Go release automation with cross-compilation and publishing.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill goreleaser-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.