go-code-review

Go code review checks error handling, goroutine usage, interface design, and concurrency safety against idiomatic patterns. It enforces wrapped errors with context, defer-based resource cleanup, context propagation, mutex-guarded shared state, consumer-defined interfaces, and exported symbol documentation while flagging naked returns and other Go pitfalls.

Go error handling requires checking all errors and wrapping them with context for debugging. The review enforces this pattern alongside proper defer usage for resource cleanup and ensures errors propagate through the call stack with meaningful information.

Concurrency safety in Go requires mutexes to guard shared state, proper context propagation to manage cancellation and deadlines, and coordinated goroutine lifecycle. The review checklist validates these patterns to prevent race conditions and resource leaks.

Interfaces in Go should be defined by their consumers, not providers, to enable flexibility and decouple dependencies. The review enforces this pattern to ensure interfaces are small, focused, and promote composability.

Yes. The checklist-based approach applies to .go files in code reviews, CI checks, or learning sessions, enabling consistent quality enforcement across teams and automated validation of idiomatic Go patterns.

Unchecked errors hide failures and make debugging difficult; unclosed resources cause leaks and instability. The review identifies these gaps and enforces checked errors with context wrapping and defer-based resource cleanup as preventive patterns.