Review and improve Go language-level correctness across numeric conversions, overflow, slices, maps, range loops, comparisons, strings, runes, UTF-8, defer evaluation, and version-dependent semantics.
NewMaintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 19 of 22 test cases with the skill, and 19 of 22 without it.
Without skill86%
With skill86%
Checks it passed that the model alone missed
Asks for or records the module's Go language version before providing range loop capture recommendations.
1 fixed18 passed either way2 still failing1 broke
Pass-rate lift
0 pp
Tokens
+6%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/16/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
I have a Go service that reads stream buffers, extracts headers into a map, and reslices data for asynchronous processing workers. Could you conduct a code review on this implementation to ensure proper slice capacity retention, map safety, and loop scope correctness? Please provide a structured audit report listing key findings with corrected code snippets.
What was checked, without and with the skill
Checked
Without skill
With skill
Asks for or records the module's Go language version before providing range loop capture recommendations.
Missed
Passed
Evaluates slice capacity retention risks when worker goroutines receive resliced buffer views without explicit memory copying.
Passed
Passed
case-01 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md44 linessingle file
Go Language Correctness
Review guarantees before implementation details. Establish the module's Go
language version, then trace representation, ownership, iteration, and text
semantics through observable behavior.
Core Workflow
Record the module and file language versions plus supported targets.
Identify external numeric, binary, and text boundaries.
Trace slice and map ownership, aliasing, capacity authority, and retention.
Review range copying, mutation, ordering, control flow, and resource scope.
Distinguish bytes, runes, UTF-8 validity, and user-perceived characters.
Separate language guarantees from compiler, runtime, and architecture details.
Add focused boundary tests and run the repository's analyzers.
Do not convert before checking sign, width, or arithmetic bounds.
Do not describe a view, reslice, or clipped capacity as an independent copy.
Do not rely on map order, append growth, bucket layout, or compiler heuristics.
Do not apply pre-Go-1.22 loop-capture advice without checking language version.
Do not call byte length, rune count, or grapheme count "characters" without defining it.
Route measured performance claims to go-performance-testing.
Source Notes
Guidance is transformed and paraphrased from Teiva Harsanyi, 100 Go Mistakes
and How to Avoid Them (Manning, 2022), especially Chapters 3-6. Examples are
original.