Apply defensive Go patterns to prevent panics and data corruption.
npx skills add https://github.com/Utchash007/TermTales --skill golang-safety-utchash007
Please help me install this Agent Skill. Skill: golang-safety Source: https://github.com/Utchash007/TermTales/tree/main/.agents/skills/golang-safety Command: npx skills add https://github.com/Utchash007/TermTales --skill golang-safety-utchash007
Defensive Go coding to prevent panics, silent data corruption, and subtle runtime bugs when working with nil-prone types, numeric conversions, resource lifecycles, or deep copies.
Apply defensive Go patterns to your codebase by guarding nils, preventing aliasing, and returning defensive copies where appropriate.
High-intent search queries and answers about installing and using this skill.
To prevent nil pointer panics in Go, apply defensive coding patterns like typed nil checks to guard interface nils and pointer values. This ensures nil-prone operations fail safely instead of crashing the program.
The best way to avoid silent data corruption from slice aliasing is to return defensive copies of slices and maps. This protects internal state from unintended modifications by external callers.
To safely handle numeric conversions in Go, apply safe conversion patterns that validate bounds before casting. This prevents overflow and subtle data corruption during numeric operations.
Yes, defensive Go patterns support safe lazy initialization, zero-value patterns, and proper defer usage. These patterns ensure resources are managed safely throughout their lifecycle without panics.
Defensive Go patterns can be applied manually during coding and reviews, but they align with Go linters to reduce common safety issues. Linters help enforce nil checks and safe conversions automatically.
tamago0224Apply defensive Go patterns to prevent panics and runtime bugs.
LuigiAPCPereiraDetect Go programming errors and enforce defensive coding practices.
osmanozenApply defensive Go patterns to prevent panics and data corruption.
copyleftdevWrite Rust code using ownership and borrowing for memory safety.
