skills/go

Review Go code diffs for concurrency, context, and error-handling anti-patterns.

Updated May 15, 2026
One-click install
npx skills add https://github.com/mattnowdev/super-review --skill skills-go
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skills/go
Source: https://github.com/mattnowdev/super-review/tree/main/skills/go
Command: npx skills add https://github.com/mattnowdev/super-review --skill skills-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers spot subtle Go anti-patterns that static analyzers often miss, reducing production bugs like goroutine leaks, broken cancellation, and incorrect error handling.

Core Features & Use Cases

  • Go concurrency + lifecycle anti-pattern detection: Identifies goroutine leaks, missing context.Context propagation, and cancellation that is never observed in select loops.
  • Correctness and error-chain hygiene: Flags typed-nil errors and missing %w error wrapping so errors.Is / errors.As work as intended.
  • Go version–specific pitfalls: Covers module-sensitive issues like loop variable capture pre-1.22, range-over-func semantics in Go 1.23, and additional newer concerns for 1.24.

Quick Start

Load this Skill when your PR diff includes *.go files (or changes go.mod/go.sum) to get an anti-pattern checklist tailored to the Go version and the code patterns in the diff.

Frequently Asked Questions about skills/go

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect goroutine leaks and context propagation issues in Go code reviews?▼

You can detect goroutine leaks and context propagation issues by applying an anti-pattern checklist to Go PR diffs, focusing on goroutine lifecycle management and ensuring `context.Context` is properly propagated and observed in select loops.

What Go version-specific concurrency pitfalls should I check during a code review?▼

During a Go code review, check for loop variable capture semantics before version 1.22, range-over-func yield handling in Go 1.23, and other version-specific concurrency traps introduced up to Go 1.24 using evidence-driven prompts.

How do I fix typed-nil errors and broken error wrapping in Go?▼

To fix typed-nil errors and broken error wrapping in Go, review diffs for anti-patterns where `%w` is missing, ensuring `errors.Is` and `errors.As` work as intended across the error chain.

Can static analyzers catch all Go concurrency and error-handling anti-patterns?▼

Static analyzers often miss subtle Go concurrency and error-handling anti-patterns, so applying an evidence-driven review checklist for missing cancellation and typed-nil errors is necessary to reduce production bugs.

When do I need to review go.mod and go.sum changes for Go concurrency traps?▼

You need to review go.mod and go.sum changes for Go concurrency traps when PRs update module dependencies, as these updates can introduce version-specific pitfalls related to loop-variable semantics and range-over-func yield handling.