Enforce defensive Go patterns for nil, slice, map, numeric, and resource safety.
npx skills add https://github.com/hellopoisonx/aim --skill golang-safety-hellopoisonx
Please help me install this Agent Skill. Skill: golang-safety Source: https://github.com/hellopoisonx/aim/tree/main/skills/golang-safety Command: npx skills add https://github.com/hellopoisonx/aim --skill golang-safety-hellopoisonx
It prevents common Go mistakes that lead to panics, silent data corruption, and subtle runtime bugs by enforcing defensive patterns around nil handling, slice/map safety, numeric conversion, and resource lifecycles.
defer is not incorrectly used inside loops.Use cases:
Ask an AI coding agent to review your Go code and refactor any nil-safety, slice/map aliasing, numeric conversion, and loop-defer patterns using the golang-safety skill guidance.
High-intent search queries and answers about installing and using this skill.
To prevent slice aliasing and backing-array retention in Go, apply defensive copying for exported getters and avoid subslices that retain the original array. This stops silent data corruption and unintended GC retention when callers mutate returned slices.
The best way to compare float values in Go without equality drift is using epsilon comparisons. Direct equality checks fail due to precision loss, so comparing the absolute difference against a small epsilon value prevents silent correctness failures.
To safely handle narrowing numeric conversions in Go, add explicit bounds checks before casting. This prevents silent truncation and overflow by verifying the source value fits within the target type's range before the unsafe conversion occurs.
Using defer inside a Go loop delays resource cleanup until the function exits, not the loop iteration. This causes resource leaks; ensure per-iteration cleanup by calling close functions directly or wrapping loop bodies in separate functions.
To fix concurrent map access panics in Go, use synchronization primitives like sync.Mutex or channels for safe concurrent writes. For non-deterministic map iteration when order matters, sort keys explicitly before iterating over the map.
tamago0224Apply defensive Go patterns to prevent panics and runtime bugs.
Utchash007Apply defensive Go patterns to prevent panics and data corruption.
dmwin72015Apply defensive Go coding practices to prevent runtime panics and data corruption.
monforjeAnalyze Go files for common errors and safety issues.