go-declarations

To prevent nil map panics in Go, initialize maps using the make function before writing to them. This Skill automatically rewrites map declarations to ensure writable maps are safely allocated and avoids runtime panics on nil map writes.

The best way to avoid shadowing in Go is to use scope-aware variable declarations and field-named struct literals. This Skill analyzes your code and rewrites declaration blocks to prevent shadowed builtins and zero-valued iota enum collisions.

Choosing between var and := in Go depends on scope, intent, and zero-value semantics. This Skill evaluates your variable declarations and applies the idiomatic initialization style that clarifies intent and prevents misleading zero values.

You should use the any type instead of interface{} in Go code to satisfy modern idiomatic requirements. This Skill reviews your declarations and updates type usage to align your production code with current Go best practices.

Yes, you can use this to review and rewrite existing Go declaration blocks. It optimizes variable declarations, constants, structs, maps, and raw string literals in production Go code and code review workflows to follow consistent project style.