Golang code style, formatting and conventions. Use when writing Go code, reviewing style, configuring linters, writing comments, or establishing project standards.
87
87%
Does it follow best practices?
Impact
87%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Control flow and condition extraction
Early returns in ValidateOrder
100%
100%
No else after return
100%
100%
Switch for Status validation
0%
100%
Named booleans in CanProcess
60%
100%
Business-meaningful boolean names
100%
100%
Initialized Items and Metadata
50%
37%
strings.Builder in ExportToCSV
100%
100%
No += in loop
100%
100%
strconv for ID conversion
100%
100%
%q in error messages
100%
100%
Capacity hint for ExportToCSV
0%
0%
Default-then-override pattern
0%
100%
Function design and struct initialization
context.Context first
100%
100%
Options struct used
100%
100%
Named fields in ServiceConfig literal
100%
100%
Named fields in all struct literals
100%
100%
Multi-line 4+ argument call
0%
100%
Closing paren on own line
0%
100%
No line over ~140 chars
100%
100%
Initialized Metadata field
0%
0%
var for zero-value fields
0%
0%
Service constant extracted
75%
100%
context.Context not in options struct
100%
100%
Logger not a standalone param
100%
100%
Package design and collection utilities
Generics not interface{}
100%
100%
Filter capacity hint
100%
0%
Map capacity hint
100%
100%
GroupBy map initialized
100%
100%
range for iteration
100%
100%
strings.Builder in Render
60%
100%
No += in Render loop
100%
100%
Internal helpers unexported
100%
100%
No blank imports
100%
100%
No dot imports
100%
100%
Pointer for Report mutation
100%
100%
NewReport returns initialized slice
0%
100%
e9761db
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.