Implements a standard Go project pipeline using Make for dependencies, linting, and testing.
Install
mkdir -p .claude/skills/go-project-conventions-rcarmo && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14309" && unzip -o skill.zip -d .claude/skills/go-project-conventions-rcarmo && rm skill.zipInstalls to .claude/skills/go-project-conventions-rcarmo
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Project conventions with module caching, linting, security checks, and tests via MakeKey capabilities
- →Clean up unused Go module dependencies
- →Format Go code
- →Execute Go security checks
- →Run Go tests
How it works
This skill uses Make targets to standardize common Go development tasks. Each target executes a specific Go command or a sequence of commands.
Inputs & outputs
When to use Go project conventions
- →Initialize Go development pipeline
- →Run project security audit
- →Standardize test execution
About this skill
Skill: Go project conventions
Goal
Provide a standard Go workflow with module caching, linting, security checks, and tests driven by Make.
Make targets (recommended)
make deps→go mod download+go mod tidymake vet→go vet ./...make lint→fmt+vet+staticcheck(if available)make security→gosec ./...(if available)make test→go test -v ./...make check→make lint && make test(standard validation pipeline)
When not to use it
- →When a project does not use Go modules
- →When a project does not use Make for task automation
Limitations
- →Requires Make to be available
- →Requires Go to be installed
- →Security checks and static analysis tools like staticcheck and gosec are only run if available
How it compares
This workflow centralizes Go development tasks under Make commands, providing a consistent interface compared to manually running individual Go commands.
Compared to similar skills
Go project conventions side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| Go project conventions (this skill) | 0 | 6mo | No flags | Beginner |
| Go project conventions | 0 | 6mo | No flags | Beginner |
| go-vuln-remediate | 0 | 1mo | Caution | Advanced |
| ark-controller-development | 2 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by rcarmo
View all by rcarmo →You might also like
Go project conventions
rcarmo
Project conventions with module caching, linting, security checks, and tests via Make
go-vuln-remediate
infobloxopen
Run Wiz-based vulnerability scan and automatic Go module remediation for containerized Go services in the konk repository. Use when you need to build images, scan CVEs, patch vulnerable dependencies in go.mod/go.sum across konk-service and konk-provision modules, validate builds, and prepare a PR su
ark-controller-development
mckinsey
Guidance for developing the Ark Kubernetes operator. Use when modifying Go types, CRDs, controllers, or webhooks. Helps with CRD generation and Helm chart sync issues.
update-go-version
grafana
Update Go version across the Tempo codebase (go.mod, tools/go.mod, Dockerfile, CI workflows, tools image tag)
releasing-software
harperreed
Use when preparing a release, tagging a version, or when user says "release", "tag", "ship it", "push to production" - ensures all release artifacts are verified before tagging to avoid the retag-four-times failure pattern
custom-builtin-functions
chainloop-dev
Create a custom builtin function to be used in the Rego policy engine