Defensive Go coding helps you avoid crashes and hidden bugs. This skill focuses on common mistakes like nil panics, slice aliasing, and silent data corruption. It is useful for any Go developer who wants safer code.
The skill covers nil safety, slice and map safety, and float pitfall handling. It shows how to write code that does not panic or corrupt data. You will learn to handle typed nil pointers, initialize maps before writing, and make defensive copies of slices.
Use this skill when writing new Go code or reviewing existing code. It is designed for AI coding agents like Claude Code. The goal is to make your Go programs more reliable and easier to debug.
Global
mkdir -p ~/.claude/skills/golang-safetyProject
mkdir -p .claude/skills/golang-safetySource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective