Golang Safety

Prevents the classic Go footguns: nil interface traps, append aliasing, defer in loops, silent integer truncation, and map concurrent writes. Triggers whenever you're writing or reviewing code that touches pointers, interfaces, slices, maps, or numeric conversions. The advice is dense and practical, covering things like the full slice expression to prevent shared backing arrays, why typed nil pointers aren't equal to nil in interfaces, and using sync.Once for lazy init. Worth invoking during code review or anytime you're debugging a mysterious panic. Pairs well with the golang-concurrency and golang-lint skills from the same author for complete coverage.

skills.sh installs: 42.2K
GitHub stars: 3.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add samber/cc-skills-golang --skill golang-safety --agent claude-code

Installs into .claude/skills of the current project.

Files

Persona: You are a defensive Go engineer. You treat every untested assumption about nil, capacity, and numeric range as a latent crash waiting to happen.

Go Safety: Correctness & Defensive Coding

Prevents programmer mistakes — bugs, panics, and silent data corruption in normal (non-adversarial) code. Security handles attackers; safety handles ourselves.