go-patterns

name	go-patterns
version	1.0.0
description	Go development patterns: testing, concurrency, errors, review, and conventions.
user-invocable	false
allowed-tools	["Read","Write","Bash","Grep","Glob","Edit","Task","Skill"]
agent	golang-general-engineer
routing	{"category":"language","force_route":true,"not_for":"'go' as a verb (go ahead, here we go, go-live, let's go), Go (the board game), pidgin/cargo english 'go do X'; only fires for the Go programming language patterns/idioms/testing or edits to .go files; SAP Commerce Cloud PHP work (use php-general-engineer agent)","triggers":[".go","go test","*_test.go","table-driven","t.Run","t.Helper","goroutine","channel","sync.Mutex","sync.WaitGroup","worker pool","fan-in","context.Context","goroutine fan-out","fmt.Errorf","errors.Is","errors.As","%w","sentinel error","Go failure mode","Go code smell","Go code review","Go PR","Go quality","sapcc","sap-cloud-infrastructure","go-bits","keppel","go-api-declarations","go-makefile-maker","make check","Go lint"],"pairs_with":["golang-general-engineer","golang-general-engineer-compact","systematic-code-review"]}

Go Patterns Skill

Umbrella skill for Go development: Google style, testing, concurrency, error handling, failure modes, code review, SAP CC conventions, and quality gates. Every Go task starts with the complete Google Go style baseline, then loads task-specific references.

Mandatory Google Style Baseline (Every Go Task)

Before reading, writing, changing, generating, debugging, or reviewing Go code:

1. Read ${CLAUDE_SKILL_DIR}/references/google-style-guide/LOAD_ORDER.md.
2. Read every file it lists, in order. Do not omit or sample parts.

Do not skip this baseline for small changes, tight context budgets, reviews, tests, or generated code. The ordered files reconstruct all four complete pinned upstream documents—overview, guide, decisions, and best practices—without excerpts. Apply their guidance to all Go code produced by the agent.

Use this precedence when guidance differs:

1. The target repository's explicit rules and required compatibility constraints.
2. The Google Go Style Guide's canonical rules.
3. Google Go Style Decisions' normative guidance.
4. Google Go Style Best Practices' non-canonical recommendations.
5. Task-specific references below.

Prefer local consistency only where the Google guide allows judgment. Do not create unrelated churn merely to restyle existing code. For new and nearby changed code, follow the current pinned guidance. Record a conscious exception when repository rules, generated-code constraints, or compatibility requirements require one.

Reference Loading Table

Signal	Load These Files	Why
Every Go task	google-style-guide/LOAD_ORDER.md, then every file it lists	Complete Google style baseline; always load every part of all four upstream documents
Testing	testing.md	Writing, fixing, or reviewing Go tests
Concurrency	concurrency.md	Goroutines, channels, sync primitives, race conditions
Error handling	error-handling.md	Error wrapping, sentinels, custom types, errors.Is/As
Review patterns	preferred-patterns.md	Detecting code smells, over-engineering, bad Go patterns
Code review	code-review.md