Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mickeyyaya/refactoring-skills --skill go-review-patternsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mickeyyaya/refactoring-skills/go-review-patterns)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/go-review-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/go-review-patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/go-review-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/go-review-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00067 | $0.03355 |
| Opus 5 | $0.00034 | $0.01677 |
| Sonnet 5 | $0.00013 | $0.00671 |
| Haiku 4.5 | $0.00007 | $0.00335 |
Grade A, and why
go-review-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Code Review Patterns
Overview
Go has a small surface area but a unique set of failure modes that do not appear in other languages. Explicit error returns, a cooperative concurrency model built on goroutines, and structural typing through interfaces create patterns that look fine to reviewers from other backgrounds but silently break under load or in error paths.
This guide focuses on six areas where Go code most commonly fails in production: goroutine leaks, context propagation gaps, error handling discipline, slice/map pitfalls, interface design mistakes, and nil traps.
Load this skill when reviewing any Go PR that touches HTTP handlers, background workers, data access layers, or any code that spawns goroutines. Cross-reference review-accuracy-calibration before posting — Go has low false positive risk overall, but goroutine and nil interface bugs are easy to miss in small diffs.
Quick Reference
| Review Dimension | Severity | Primary Red Flag |
|---|---|---|
| Goroutine leak | HIGH | go func() with no termination path in the spawning scope |
| Missing context cancellation | HIGH | Goroutine does I/O with no ctx.Done() case in select |
| Context stored in struct | MEDIUM | type Foo struct { ctx context.Context } |
| Context not passed to I/O | MEDIUM | db.Query(sql) instead of db.QueryContext(ctx, sql) |
| Ignored error on I/O | HIGH | f, _ := os.Open(...) — error discarded with blank identifier |
Error compared with == |
HIGH | if err == ErrNotFound instead of errors.Is(err, ErrNotFound) |
| Nil map write | CRITICAL | var m map[string]int; m["key"] = 1 — panics at runtime |
| Nil interface trap | HIGH | Returning typed nil as error — never nil-checks to true |
| Concurrent map read/write | CRITICAL | Map accessed from multiple goroutines without sync.RWMutex |
| Slice append aliasing | MEDIUM | Shared underlying array after append with sufficient capacity |
| Exported interface from impl package | MEDIUM | Interface defined in same package as its only implementation |
defer inside loop |
HIGH | defer f.Close() in for loop — defers accumulate until function exit |
init() with side effects |
MEDIUM | func init() dialing network, registering globals, reading files |
Empty interface{} / any abuse |
LOW–MEDIUM | Public API fields typed any masking a design problem |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 318 lines · 67 tokens per session scan A 2fca8a87ea00
go-review-patterns is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 67 tokens to every session and 3,355 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
pr-to-go-linter
Generate a new pkg/linters analyzer from a merged or open PR pattern.
golang-refactoring
Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, gofmt -r, gopatch), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code…
sapcc-review
Gold-standard SAP CC Go code review: 10 parallel domain specialists.
go-concurrency-safety
L1 supplement - audits Go-specific concurrency hazards in node client code: map iteration non-determinism, goroutine leaks, mutex ordering, panic boundaries, context cancellation.
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.
agents-md
Generate AGENTS.md files for Go, Rust, TypeScript, and Java projects. Use this skill whenever the user asks to create, scaffold, bootstrap, update, or review an AGENTS.md (or agent-instructions, CLAUDE.md, repo guide for agents) file in a codebase. Also trigger when the user says "add AGENTS.md", "make this repo…