go-best-practices

Idiomatic Go code is enforced by applying guidelines from Effective Go, Go Code Review Comments, and the Google Go Style Guide to naming, error handling, and package organization for maintainability. This prevents subtle bugs and style drift across the team.

Handling errors and concurrency in Golang code reviews involves checking for idiomatic error wrapping and safer concurrency primitives. This skill provides actionable recommendations to improve correctness and clarity in channel usage and error propagation.

Refactoring Go interfaces and packages requires consulting the Google Go Style Guide to optimize organization for discoverability. This skill distills those authoritative recommendations to guide interface refinements and clearer package structures.

Choosing concurrency primitives in Go depends on the specific synchronization requirements of your code. This skill reviews your implementation against Effective Go and Go Code Review Comments to recommend safer, clearer concurrency patterns and channel usage.

Yes, writing clearer tests for Golang applications is a core feature of this approach. It advises on test additions and improvements based on authoritative Go style guides to ensure your testing practices remain idiomatic and maintainable.