Language-specific review guidance for Go code including idiomatic patterns, test conventions, and build commands
Reviews Go code for idiomatic patterns, test conventions, and build verification.
npx claudepluginhub openshift-eng/ai-helpersThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides Go-specific guidance for code quality reviews. It is loaded automatically by the pre-commit-review command when --language go is specified or when .go files are detected among the changed files.
Use this skill when reviewing Go source code. Its sections are referenced during the unit test coverage, idiomatic code, and build verification review steps.
t.Run() for subtests to provide clear test case identificationt.Parallel() at the top of test functions and subtests where tests are independent-race flag — avoid shared mutable state between parallel tests_test.go suffixt.Helper() in test helper functions so failure messages report the caller's line numberFollow the conventions in Effective Go and the Go Code Review Comments wiki. Key reminders:
gofmt. Unformatted code is a blocking issueMixedCaps / mixedCaps. Avoid stuttering (http.Server not http.HTTPServer). Acronyms are all caps (URL, HTTP, ID)fmt.Errorf("context: %w", err) to preserve the chain for errors.Is() / errors.As()context.Context as the first parameter to functions that perform I/O or may be long-runningUse the following commands in priority order during build verification:
make test if a Makefile with a test target exists; otherwise go test -race ./...make verify if available; otherwise go vet ./...make build if available; otherwise go build ./...