go
Idiomatic Go: interfaces, error handling, concurrency, testing, package layout, and debugging. Use when user pastes Go code, asks 'is this idiomatic', 'should this be an interface', 'how should I structure this', writes/reviews goroutines, channels, select, sync.* primitives or errgroup, designs error returns (fmt.Errorf, errors.Is/As/Join, panic/recover, sentinels, custom error types), writes _test.go files (table-driven, subtests, t.Parallel/Helper/Cleanup, testify, mocks, fuzzing), debugs Go test failures, races, deadlocks, panics, or stack traces, organizes packages (naming, internal/, layout), or asks any open Go question that doesn't fit a more specific child skill. SKIP for Go performance/profiling work — use go-profiling-optimization instead.
Code Review20 files