Go Modern Review (1.25 + 1.26)

Use this skill to find actionable Go adoption opportunities during review or refactor work after upgrading to Go 1.25 or 1.26. Prioritize changes that improve correctness, clarity, safety, maintainability, or test ergonomics. Do not force mechanical churn for features that add no material value.

First, confirm which Go version the package targets and scope recommendations to that version (or higher). If both apply, prefer the newer pattern.

Review Workflow

1. Confirm the package's Go version, or that the user explicitly wants forward-looking recommendations.
2. Start with the highest-value adoption points for the target version (see the per-version shortlists below).
3. On Go 1.26, run or consider go fix modernizers before doing manual cleanup.
4. Check for deprecations, tightened validation, or behavioral changes that should influence refactors.
5. Recommend toolchain and operational follow-ups where relevant (vet analyzers, runtime/metrics, flight recorder, etc.).
6. Keep recommendations ranked:
   • correctness and security first
   • maintainability and tooling second
   • testability and observability third
   • readability and stylistic cleanups last