Go project conventions

Automate Go project workflows with Makefile targets for vetting, linting, security, and tests.

147|5|Updated Jan 11, 2026

Search Tags:#testing #security #golang #go #lint #makefile

Ready to run

npx skills add https://github.com/rcarmo/agentbox --skill go-project-conventions-rcarmo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Go project conventions
Source: https://github.com/rcarmo/agentbox/tree/main/skel/.github/skills/go
Command: npx skills add https://github.com/rcarmo/agentbox --skill go-project-conventions-rcarmo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go projects often lack standardized workflows; this Skill defines a consistent Makefile-driven approach for module caching, vetting, linting, security checks, and tests.

Core Features & Use Cases

Makefile-driven workflow: Targets for deps, vet, lint, security, test, and check to enforce best practices.
Performance & security: Module caching speeds builds; integrated tools like golangci-lint and gosec improve code quality and security.
Use Case: When starting a new Go project, apply these conventions to ensure reproducible builds and code quality checks across local development and CI.

Quick Start

Run make check in your Go project to apply module caching, vet, lint, security checks, and tests.

Frequently Asked Questions about Go project conventions

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

FAQPage Schema

How do I standardize Go project workflows with a Makefile?▼

To standardize Go project workflows, you need a Makefile with specific targets for deps, vet, lint, security, test, and check. This enforces consistent module caching, quality scanning, and testing across local and CI environments.

What is the best way to run linting and security scanning in a Go project?▼

The best way to run linting and security scanning in a Go project is by integrating golangci-lint and gosec into a standardized Makefile. This automates code quality checks and vulnerability scanning during your regular build process.

How do I set up a Makefile for Go module caching and testing?▼

Set up a Makefile for Go module caching and testing by defining targets like deps, test, and check. Running make check applies module caching to speed up builds, then automatically executes vetting, linting, security scanning, and tests.

Do I need a Makefile to use golangci-lint and gosec in my Go pipeline?▼

Yes, this approach requires a Makefile to drive the workflow. The Makefile must define targets for deps, vet, lint, security, test, and check to properly orchestrate golangci-lint and gosec within your Go pipeline.

Can I use this Go workflow convention for both local development and CI?▼

Yes, these Go workflow conventions apply to typical Go project pipelines, local development, and CI workflows. By running make check, you ensure reproducible builds and consistent code quality checks across all environments.

Why should I use a Makefile for Go project vetting and tests?▼

Using a Makefile for Go project vetting and tests solves the problem of lacking standardized workflows. It defines a consistent approach for module caching, vetting, linting, security checks, and tests, ensuring reproducible builds and code quality.