What problem does it solve? Go code often ships with subtle runtime bugs: swallowed errors, nil map panics, typed-nil interface traps, silent integer truncation, and shared slice backing arrays. This Skill provides a systematic checklist and deep references to write and review Go code that handles errors correctly and guards every nil, pointer, slice, and numeric edge. ## Core Features & Use Cases - Error Handling Discipline: Enforces checking and wrapping every error with %w, inspecting with errors.Is/errors.As/errors.Join, and applying the single handling rule (log XOR return) with a clear panic policy. - Defensive Coding Guards: Covers comma-ok type assertions, nil map initialization, append backing-array traps, defensive copying with slices.Clone/maps.Clone, integer bounds checks, float epsilon comparison, and safe zero-value design. - Use Case: When reviewing a Go pull request, activate this Skill to audit the diff for discarded errors, log-and-return duplicates, bare type assertions, and unguarded numeric conversions before merge. ## Quick Start Review this Go diff for error handling mistakes, nil safety issues, and numeric pitfalls using the go-safety guidelines.
