Standardizes Go project operations including security scanning, linting, and test coverage.
Install
mkdir -p .claude/skills/go-rcarmo && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14310" && unzip -o skill.zip -d .claude/skills/go-rcarmo && rm skill.zipInstalls to .claude/skills/go-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.
go — an agent skill by rcarmo.Key capabilities
- →Run static analysis with `go vet`
- →Perform linting with `golangci-lint`
- →Conduct security checks with `gosec`
- →Execute tests with race detection and coverage analysis
- →Run a standard validation pipeline combining vet and lint
How it works
The skill provides a standard Go workflow using Make targets to automate common development tasks. It includes commands for dependency management, static analysis, linting, security checks, and testing.
Inputs & outputs
When to use go
- →Lint Go code
- →Run tests with coverage
- →Check for security vulnerabilities
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+ installgolangci-lintandgosecif missingmake vet→go vet ./...make lint→golangci-lint run --timeout=5mmake security→gosec ./...make test→go test -v -race -coverprofile=coverage.out ./...make check→make vet && make lint
When not to use it
- →When `golangci-lint` or `gosec` are not available
Limitations
- →`golangci-lint` and `gosec` are used if available
How it compares
This skill standardizes Go development tasks through Make targets, integrating dependency management, static analysis, linting, security checks, and testing into a consistent workflow, which is more automated than running each tool manually
Compared to similar skills
go side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| go (this skill) | 0 | 6mo | No flags | Beginner |
| test-fuzz-gen | 0 | 2mo | No flags | Intermediate |
| codeql | 1 | 2mo | Review | Advanced |
| go-dev-guidelines | 14 | 9mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by rcarmo
View all by rcarmo →You might also like
test-fuzz-gen
justincranford
Generate _fuzz_test.go fuzz tests conforming to cryptoutil project standards. Use when adding fuzz coverage for parsers, decoders, or crypto input handling to ensure correct build tags, 15s minimum fuzz time, seed corpus, and safe assertion patterns.
codeql
trailofbits
Runs CodeQL static analysis for security vulnerability detection using interprocedural data flow and taint tracking. Applicable when finding vulnerabilities, running a security scan, performing a security audit, running CodeQL, building a CodeQL database, selecting query rulesets, creating data extension models, or processing CodeQL SARIF output. NOT for writing custom QL queries or CI/CD pipeline setup.
go-dev-guidelines
jumppad-labs
This skill should be used when writing, refactoring, or testing Go code. It provides idiomatic Go development patterns, TDD-based workflows, project structure conventions, and testing best practices using testify/require and mockery. Activate this skill when creating new Go features, services, packages, tests, or when setting up new Go projects.
code-formatting
openshift
MANDATORY: When writing Go tests, you MUST use 'When...it should...' format for ALL test names. When writing any Go code, you MUST remind user to run 'make lint-fix' and 'make verify'. These are non-negotiable HyperShift requirements.
tidb-test-guidelines
pingcap
Decide where to place TiDB tests and how to write them (basic structure, naming, testdata usage). Use when asked about test locations, writing conventions, shard_count limits, casetest categorization, or when reviewing test changes in code review.
go-table-driven-tests
Xe
Write Go table-driven tests following Go community best practices and this repository's conventions. Use when writing or refactoring Go tests, especially when you notice repeated test patterns or copy-pasted test code.