go-review

To review Go code for idiomatic patterns, analyze git diffs to surface anti-patterns and apply staticcheck to validate correctness. This identifies subtle concurrency pitfalls and suggests concrete, safe improvements.

The best way to run go vet and staticcheck on modified Golang files is to inspect the git diff and execute these tools against the changed code. This surfaces defects and validates safety before merging.

To check Golang code changes for safe concurrency and proper error handling, review the modified files against idiomatic patterns. Applying static analysis tools like go vet helps detect brittle error handling and concurrency pitfalls.

Yes, the Go code review process reports findings by severity. It analyzes code changes to surface potential issues and provides prioritized, actionable recommendations to improve code quality before merging.

Yes, you can use staticcheck and go vet to find performance bottlenecks in Go code. Applying these tools during code review validates correctness and surfaces anti-patterns that may impact performance.