go-makefile

Standardize Go service builds with a unified Makefile enforcing CI-parity quality gates.

1|Updated Jun 20, 2026

Search Tags:#architecture #linting #go #coverage #makefile #ci #govulncheck

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill go-makefile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: go-makefile
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/go-makefile
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill go-makefile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires golangci-lint, govulncheck, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the drift between local development and CI environments by enforcing a unified, fail-fast Makefile contract that ensures every verification gate runs identically on any machine.

Core Features & Use Cases

CI-Parity Enforcement: Guarantees that local commands and CI pipeline steps are identical, preventing "works on my machine" bugs.
Fail-Fast Quality Gates: Orchestrates a cost-optimized execution order (tidy, generate, vet, lint, arch, vuln, cover) to catch errors as cheaply as possible.
Architectural Governance: Automates the Dependency Rule via fitness functions, ensuring domain, application, and infrastructure layers remain decoupled.

Quick Start

Use the go-makefile skill to initialize the standard CI-parity Makefile and quality gate scripts in your current Go service directory.

Frequently Asked Questions about go-makefile

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

FAQPage Schema

How do I enforce CI-parity for Go service build tasks locally?▼

Enforce CI-parity for Go service build tasks by running a unified Makefile contract that executes verification gates identically across local and CI environments, preventing drift. It orchestrates linting, testing, and vulnerability scanning consistently.

How do I automate architectural fitness functions in a Go Makefile?▼

Automate architectural fitness functions in a Go Makefile by applying the Dependency Rule to ensure domain, application, and infrastructure layers remain decoupled. This governance gate validates layer invariants during the build process.

What is the best way to run govulncheck and golangci-lint in a Go CI pipeline?▼

Run govulncheck and golangci-lint in a Go CI pipeline by orchestrating a fail-fast execution order within a standard Makefile. This sequence catches lint and reachable-call-graph vulnerabilities cheaply before deeper tests run.

Does this Makefile approach support race-detector-always-on testing for Go?▼

Yes, this Makefile approach supports race-detector-always-on testing for Go. It standardizes backend verification processes to satisfy strict race detection and coverage enforcement requirements across all executed test gates.

Why does my Go CI pipeline pass but local linting and coverage fail?▼

Go CI pipelines pass while local linting fails due to environment drift. A unified Makefile eliminates this by enforcing identical execution order and quality gates, ensuring race detection and coverage checks run consistently.

What execution order should a Go Makefile use for quality gates?▼

A Go Makefile should use a cost-optimized fail-fast execution order: tidy, generate, vet, lint, arch, vuln, and cover. This sequence catches formatting and linting errors cheaply before running expensive vulnerability scans.