Go Optimizer

Use this skill for Go code where security and speed both matter. Treat performance work as a measurement problem and security work as a correctness boundary problem.

Core Principles

• Measure before changing code. Keep baseline numbers and compare after each patch.
• Prefer small, local improvements with clear evidence over broad rewrites.
• Security constraints outrank speed. Never optimize by weakening validation, auth, crypto, permissions, or error handling.
• Keep Go idiomatic. Favor standard library primitives and simple data flow unless profiling proves otherwise.
• Stop when the next candidate has no defensible evidence or the risk outweighs the gain.

Workflow

1. Scope
   • Identify the hot path, security boundary, and user-visible operation.
   • Check current git state and preserve unrelated user changes.
   • Find existing benchmarks, tests, and integration paths before adding new ones.