golang-safety

To prevent nil pointer panics in Go, enforce defensive practices like checking interfaces and pointers before use. This Skill identifies potential nil issues to ensure robust code execution.

The best way to handle type assertions safely in Go is using the comma-ok pattern or type switches. This approach prevents runtime panics by checking assertion success before proceeding with the asserted type.

To avoid data races during concurrent map access in Go, apply proper synchronization patterns. This Skill advises on safe concurrent access to maps and slices, reducing synchronization bugs in concurrent operations.

To check a Go source file for resource leaks and safety anti-patterns, review the code for deferred resource management and nil map writes. This Skill enforces best practices to prevent runtime panics and security issues.

Fixing Go safety issues does not require external tools or dependencies. This Skill provides safety patterns from coding to concurrent operations using standard defensive practices without needing additional software.