Identify nil-related panics and runtime bugs in Go code.
npx skills add https://github.com/mrlorentx/.files --skill golang-safety-mrlorentx
Please help me install this Agent Skill. Skill: golang-safety Source: https://github.com/mrlorentx/.files/tree/main/ai/claude/skills/golang-safety Command: npx skills add https://github.com/mrlorentx/.files --skill golang-safety-mrlorentx
Defensive Go coding to prevent panics, silent data corruption, and subtle runtime bugs. Use whenever writing or reviewing Go code that involves nil-prone types (pointers, interfaces, maps, slices, channels), numeric conversions, resource lifecycle (defer in loops), or defensive copying. Also triggers on questions about nil panics, append aliasing, map concurrent access, float comparison, or zero-value design.
Analyze the Go codebase to identify nil-safety gaps and apply defensive patterns to prevent panics and subtle bugs.
High-intent search queries and answers about installing and using this skill.
Prevent nil panics in Go by enforcing defensive patterns like nil-safety checks and zero-value design before accessing pointers, maps, slices, channels, or interfaces. This ensures robust runtime safety during code execution.
The best way to handle defer in loops is applying safe defer usage patterns to prevent resource leaks and subtle runtime bugs. Defensive Go practices ensure resources are released correctly without causing lifecycle issues.
Stop silent data corruption from append aliasing and map concurrent access by applying defensive copying and concurrency safety patterns. These practices prevent shared memory issues across Go routines.
Yes, defensive Go safety checks work for code review, architecture reviews, and automated checks across existing projects. It identifies nil-safety gaps and applies defensive patterns to prevent panics and subtle bugs.
Go code panics during type conversions and float comparisons when defensive coding patterns are missing. Applying best practices for safe type conversions and numeric handling prevents these subtle runtime bugs.
JamesPrialInitialize Go maps with make before writes to prevent nil map panics.
samberAnalyze Go functions for nil safety risks and unsafe conversions.
ozan-fnAnalyze Go code for nil safety, concurrency, and resource management issues.
JylhisDetect Go runtime panics and silent data corruption risks.
