golang-safety

To prevent nil pointer dereferences and silent data corruption in Go, use static analysis to detect nil panics, mitigate slice aliasing, and enforce safe initialization. This Skill applies defensive coding to resolve these runtime issues.

The best way to fix concurrent map access and slice aliasing issues in Golang is running static analysis to identify unsafe patterns. This Skill mitigates these issues by enforcing defensive copying for shared data and safe append behaviors.

Yes, you need golangci-lint installed to check Go code safety. This Skill requires both golangci-lint and go for static analysis and code execution to identify numeric overflows and enforce best coding standards.

Defensive coding handles numeric overflows and goroutine resource management by ensuring safe type conversions, correct numeric comparisons, and properly managing deferred operations. This Skill automatically identifies these resource safety issues during code review.

You should use defensive copying for shared data structures in Go whenever multiple variables reference the same underlying slice or map. This Skill encourages immutability practices to prevent silent data corruption during concurrent operations.