Enforce defensive Go coding patterns to prevent panics and silent data corruption.
npx skills add https://github.com/dashkan/pivox --skill golang-safety-dashkan
Please help me install this Agent Skill. Skill: golang-safety Source: https://github.com/dashkan/pivox/tree/main/.agents/skills/golang-safety Command: npx skills add https://github.com/dashkan/pivox --skill golang-safety-dashkan
Defensive Golang coding eliminates common correctness failures in normal Go programs that otherwise lead to panics, subtle runtime bugs, and silent data corruption.
Use the golang-safety skill when reviewing a Go function that could panic or corrupt data, and ask it to produce a safer rewrite with nil checks, defensive copies, and overflow/bounds validation where applicable.
High-intent search queries and answers about installing and using this skill.
Prevent nil interface panics in Go by applying defensive nil checks for interfaces, pointers, maps, slices, and funcs to stop typed-nil traps and runtime panics from nil map writes or nil function calls.
Slice data corruption in Go happens due to append aliasing and subslice backing-array retention. Avoid this by applying defensive copying patterns for exported collection getters to prevent silent data modification.
The best way to compare floating-point numbers in Go is using epsilon comparisons for float equality and reconciliation logic, which prevents silent precision errors that direct equality checks cause.
Fix defer-in-loop resource leaks in Go by ensuring proper cleanup executes per iteration rather than deferring until function return, which prevents goroutine lifecycle issues and resource exhaustion.
Stop integer overflow and truncation in Go numeric conversions by enforcing bounds checks for narrowing conversions, ensuring values fit within target type limits before casting to prevent silent data corruption.
tamago0224Apply defensive Go patterns to prevent panics and runtime bugs.
hellopoisonxEnforce defensive Go patterns for nil, slice, map, numeric, and resource safety.
adibfirmanReview Go code for nil safety, slice/map ownership, numeric conversions, and resource lifecycles.
samberAnalyze Go functions for nil safety risks and unsafe conversions.
