golang-continuous-integration
golang continuous integration
What it does
- goreleaser: go install github.com/goreleaser/goreleaser/v2@latest
- gh: brew install gh
- -race: CI MUST run tests with the -race flag (catches data races — undefined behavior in Go)
- -shuffle=on: Randomize test order to catch inter-test dependencies
- -coverprofile: Generate coverage data
- git diff --exit-code: Fails if go mod tidy changes anything
- default: Standard security queries
Requirements & configuration
- Programs need cross-compiled binaries, archives, and optionally Docker images.
- Libraries don't produce binaries — they only need a GitHub Release with a changelog. Use a minimal config that skips the build.
- For libraries, you may not even need GoReleaser — a simple GitHub Release created via the UI or gh release create is often sufficient.
- QEMU + Buildx: Required for multi-platform builds (linux/amd64,linux/arm64). Remove platforms you don't need.
- Provenance + SBOM: provenance: mode=max and sbom: true generate supply chain attestations. These require attestations: write and id-token: write permissions.
Configuration: DOCKERHUB_USERNAMEDOCKERHUB_TOKENGITHUB_TOKEN
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
golang-continuous-integration FAQ
What does the golang-continuous-integration skill do?
CI/CD pipeline configuration using GitHub Actions for Golang projects — testing, linting, SAST, security scanning, code coverage, Dependabot, Renovate, GoReleaser, code review automation, and release pipelines. Use when setting up or improving Go project CI, configuring GitHub Actions workflows, adding linters or security scanners, automating dependency updates, or adding quality gates. goreleaser: go install github.com/goreleaser/goreleaser/v2@latest gh: brew install gh
What does golang-continuous-integration require?
Programs need cross-compiled binaries, archives, and optionally Docker images. Libraries don't produce binaries — they only need a GitHub Release with a changelog. Use a minimal config that skips the build. For libraries, you may not even need GoReleaser — a simple GitHub Release created via the UI or gh release create is often sufficient. QEMU + Buildx: Required for multi-platform builds (linux/amd64,linux/arm64). Remove platforms you don't need. Provenance + SBOM: provenance: mode=max and sbom: true generate supply chain attestations. These require attestations: write and id-token: write permissions. Configuration keys: DOCKERHUB_USERNAME, DOCKERHUB_TOKEN, GITHUB_TOKEN.
How do I install golang-continuous-integration?
Run: npx -y skills add https://github.com/samber/cc-skills-golang --skill golang-continuous-integration --agent claude-code — the source lives at github.com/samber/cc-skills-golang.
Maintain golang-continuous-integration?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/samber-cc-skills-golang-golang-continuous-integration?ref=badge) npx agentictools info skills/samber-cc-skills-golang-golang-continuous-integration The second line is the CLI lookup for this page — handy in READMEs and docs.
Related skills
anti-detect-browser Launch Chromium with real-device fingerprints for multi-account operations, web scraping, and AI agent automation.
recipe-email-drive-link Share Google Drive files and email access links to recipients in a single workflow.
recipe-create-gmail-filter Automated Gmail message routing through filters that label, star, or archive incoming mail.
recipe-save-email-attachments Automated workflow to find Gmail attachments and save them to Google Drive folders.
firecrawl-build-search Web search discovery and source ranking for query-driven workflows.
firecrawl-build-onboarding Authenticate Firecrawl and set up SDK integration in a project.