golang-continuous-integration

Configures GitHub Actions CI/CD pipelines for Go projects covering testing, linting, security scanning, and releases.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/VerifiedOrganic/onboard --skill golang-continuous-integration-verifiedorganic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: golang-continuous-integration
Source: https://github.com/VerifiedOrganic/onboard/tree/main/.agents/skills/golang-continuous-integration
Command: npx skills add https://github.com/VerifiedOrganic/onboard --skill golang-continuous-integration-verifiedorganic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go, goreleaser, gh, and includes references (resource) and assets (resource) components.

What problem does it solve? Setting up a production-grade CI/CD pipeline for a Go project involves dozens of decisions — test flags, lint configuration, security scanners, dependency update automation, release tooling, and repository security settings — and getting any of them wrong leads to flaky builds, missed vulnerabilities, or unsafe automation. This Skill provides audited, ready-to-adapt GitHub Actions workflows and configurations so nothing critical is forgotten. ## Core Features & Use Cases - Complete workflow templates: Test (with -race, -shuffle=on, coverage), integration tests with service containers, golangci-lint, security scanning (govulncheck, gosec, CodeQL, Bearer), Docker multi-platform builds with SBOM/provenance, and GoReleaser release pipelines for CLIs, libraries, and monorepos. - Dependency automation: Dependabot and Renovate configurations with minor/patch grouping, plus an auto-merge workflow with documented security guardrails. - AI-driven code review: Claude Code Action and GitHub Copilot review setups that apply Go-specific review skills across quality, correctness, security, and performance jobs. - Use Case: You just created a new open-source Go library and need CI before the first external contribution. The Skill generates the test, lint, security, and release workflows, configures Dependabot, and walks you through branch protection and least-privilege token settings. ## Quick Start Ask the agent to set up a complete GitHub Actions CI pipeline for your Go project, including tests, linting, security scanning, and a GoReleaser release workflow.

Frequently Asked Questions about golang-continuous-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a GitHub Actions CI pipeline for a Go project?▼

Create workflows in this order: test, lint, security, then release. The test workflow runs go test with -race, -shuffle=on, and -coverprofile across a Go version matrix with fail-fast disabled, and the lint workflow runs go vet plus golangci-lint on every pull request.

What security scanning tools should Go CI use?▼

Use govulncheck for call-path-aware vulnerability detection, gosec for Go-specific SAST, CodeQL with the security-and-quality query suite, and Bearer for sensitive data flow issues. Upload results as SARIF so they appear in the repository's Security tab.

Renovate vs Dependabot for Go dependency updates?▼

Renovate is the more configurable option: it runs go mod tidy automatically via gomodTidy, supports native automerge without a separate workflow, and handles monorepos and Go workspaces. Dependabot is simpler and built into GitHub but needs a separate workflow for auto-merge.

How do I configure GoReleaser for a Go library with no binary?▼

Set builds to skip: true so GoReleaser only generates a changelog and GitHub Release. Libraries produce no artifacts, so a minimal config works — or skip GoReleaser entirely and create the release with gh release create.

Why do Go integration tests pass against broken services in CI?▼

Go caches test results, so tests can pass without re-running against the actual services. Run integration tests with -count=1 to disable caching, and use GitHub Actions service containers with health checks for dependencies like PostgreSQL and Redis.

Is it safe to auto-merge Dependabot pull requests in GitHub Actions?▼

Auto-merge requires elevated contents: write and pull-requests: write permissions, so restrict it with an if: github.actor == 'dependabot[bot]' guard and exclude major updates. Since actor checks are not fully spoof-proof, branch protection with required status checks is the real safety net.