Go Engineering · fabork-security bundle Write, design, and review Go the way experienced Go engineers do — idiomatic Go, API and interface design, generics, pointers vs values, error handling, concurrency, package boundaries, naming, documentation, testing, and code review. Covers structural correctness (data races, goroutine leaks, swallowed errors, context and resource handling) alongside design and style; it does not judge semantic correctness, so it will not tell you whether the code does what your requirements say. Use when writing or changing .go files, designing a Go package or public API, reviewing a Go diff or PR, deciding whether something is idiomatic Go, or running golangci-lint. Synthesizes Effective Go, the Google Go Style Guide, and Go Code Review Comments.
