Go Coding Guidelines

What it does

A compact, practical guide for writing production-quality Go. The document codifies rules and examples around pooled resource lifetimes, safe concurrency patterns, numeric size handling, robust error handling, and disciplined testing practices. It focuses on avoiding common pitfalls that cause races, memory issues, and flaky tests.

When to use it

Refer to these guidelines during code review, when authoring concurrent or pooled-resource code, before changing APIs that affect ownership semantics, and when writing tests that depend on GC or allocation expectations. Also useful as an input to automated repair/workflow coders that enforce project conventions.

What's included

• Scripts: none listed
• References: none listed
• Instructions: concrete code examples and checklists (pool.Release ownership rules, using os.CreateTemp + os.Rename for atomic writes, singleflight for duplicate writes, bounded goroutine pools, explicit numeric conversions, and error-wrapping patterns). The SKILL includes a quick pre-commit checklist.

Compatible agents

Developer assistance agents, review automation, and workflow coders that embed project-specific fix prompts (e.g., workflow-coder).