go-code-review

To review Go code for concurrency bugs and idiomatic issues, apply a structured checklist to source files and diffs that identifies nil safety faults, race conditions, and non-idiomatic patterns. This process yields severity-classified findings with concrete fix recommendations.

The best way to check Go pull requests for error handling and API design faults is evaluating changed files against Go best practices. This produces a severity-classified report of BLOCKERS, WARNINGS, and SUGGESTIONS tied to package boundaries and exported APIs.

Yes, you can audit legacy Golang modules for testing gaps and package layout problems. Perform module-level reviews across packages by accessing Go source files, tests, and go.mod to evaluate test coverage and modernize outdated code structures.

Classify severity when reviewing Go code before merge by grouping findings into BLOCKER, WARNING, and SUGGESTION categories. This classification prescribes concrete fixes and rationale based on correctness, concurrency, and error handling constraints.

To perform a structured Golang code review, you need access to Go source files, tests, go.mod, and context about intended behavior and runtime constraints. These inputs allow the evaluation of exported APIs, concurrency patterns, and test coverage.

This Go code review process works for both individual files and full pull requests. It applies to individual Go files, diffs in pull requests, and module-level reviews across packages depending on the required evaluation scope.