go-code-review

Perform a structured Go code review by applying a checklist based on Go Wiki CodeReviewComments to identify issues in formatting, error handling, naming, concurrency, and security. This enforces consistent quality across Go projects of all sizes during pull requests.

Check for Go code quality issues like improper error propagation, ignored errors, missing documentation, and incorrect goroutine synchronization. A structured review checklist enforces explicit criteria for interfaces, data structures, and security practices to identify these common problems.

Yes, this code review checklist applies to Go projects of all sizes, including onboarding new contributors. It provides a quick-reference guide to help teams identify common issues and maintain consistent quality across Go codebases during the onboarding process.

Enforce Go formatting and error handling conventions by applying explicit, checkable criteria during code reviews. Verify code is formatted with gofmt or goimports and check for proper error propagation to avoid ignored errors, ensuring codebase consistency.

The best way to review Go concurrency and interface design is using a quick-reference checklist that applies explicit criteria for goroutine usage, synchronization, and interface clarity. This ensures safety and maintains coherent package layout during code reviews.

Yes, you can use this checklist to check Go package structure and naming conventions. It enforces clear naming conventions and coherent package layout, helping teams identify structural issues and maintain consistent quality across their Go codebases.