“Go”

Go engineering standards for this repo — package layout, error handling, logging, testing, concurrency and design patterns.

Index and routing table for this repository's Go skills: maps a task to the skill that owns it, names the secondary skills worth loading alongside, and draws…

Safe refactoring workflow for Go: behavior-preserving steps, compiler-checked renames, extracting packages, breaking circular dependencies, and strangler…

Profile and optimize Go CPU, allocations, GC, concurrency, and I/O with benchmarks and pprof.

Go error handling patterns, wrapping, sentinel errors, custom error types, and the errors package.

How Go tests are written in these repos: assertions, tables, test doubles, helpers, async waits, golden files, fuzzing, benchmarks, and integration tests…

Go testing patterns for production-grade code: subtests, test helpers, fixtures, golden files, httptest, testcontainers, fuzz testing, and testing/synctest.

Correct use of Go's built-in data structures: slices (nil vs empty, append semantics, aliasing, preallocation), maps (comma-ok, sets, iteration order)…

Structured logging, distributed tracing, metrics, and health checks for Go services.

Review design specification documents for Go programs before implementation begins.

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files.

Apply a compact, Go-version-aware rulebook derived from the 100 numbered mistakes cataloged by 100go.co when writing, reviewing, debugging, refactoring…

Implement or review Go behavior with targeted tests, ownership and concurrency evidence.

Go development standards, Effective Go, and tooling.

Diagnose runtime problems in Go programs: panics and stack traces, deadlocks, goroutine leaks, memory leaks, OOM kills, race reports, and debugging with delve…

Question a Go plan, spec, or design with the Go proverbs from Rob Pike's Gopherfest 2015 talk.

Go (Golang) patterns, concurrency, interfaces, error handling, and idiomatic Go development for high-performance systems

Prevent panics, silent corruption, and subtle runtime bugs in Go: typed-nil interfaces, slice aliasing, integer overflow on conversion, float comparison…

Dependency injection in Go: constructor injection, wiring in main, avoiding global state, and when frameworks (wire, fx, dig) earn their complexity.

Use Go 1.26 features correctly.

Use Go 1.27 features correctly.

Use when the user explicitly says they are mobile ('go mobile', 'going mobile', 'heading out', 'on my phone'), when a message arrives via the phone bridge, or…

Comprehensive Go style, code review, and best practices guide based on Effective Go, Go Code Review Comments, and Google Go Style Guide.

Task workflow controller for Codex.