go-reviewer

Review Go projects for idiomatic patterns, error handling, concurrency safety, and interface design.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/physics91/claude-vibe --skill go-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-reviewer
Source: https://github.com/physics91/claude-vibe/tree/main/skills/go-reviewer
Command: npx skills add https://github.com/physics91/claude-vibe --skill go-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce idiomatic Go patterns, robust error handling, concurrency safety, and clean interface design, reducing review time and boosting code quality.

Core Features & Use Cases

  • Error handling checks: enforce context wrapping, avoid ignored errors, and encourage meaningful messages.
  • Concurrency safeguards: detect data races, goroutine leaks, and proper synchronization.
  • Interface design: promote small, testable interfaces that improve testability and maintainability.
  • Testing guidance: suggests table-driven tests, benchmarks, and go test strategies.
  • Use Case: Quick Go project review highlighting critical anti-patterns before merge.

Quick Start

Run the go-reviewer skill against a repository containing a go.mod at the project root to receive an idiomatic-Go review summary.

Frequently Asked Questions about go-reviewer

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

FAQPage Schema
How do I review Go code for idiomatic patterns and best practices?

Go code review checks idiomatic patterns, error handling with context wrapping, concurrency safety, and interface design. Run the reviewer against a repository with go.mod at the root to receive a summary of anti-patterns and coding standard violations across your project.

What concurrency issues does Go code review detect?

Concurrency review identifies data races, goroutine leaks, and improper synchronization like missing mutex usage. It enforces context cancellation patterns and safe goroutine lifecycle management to prevent concurrent access bugs.

Can I automate Go error handling checks in code review?

Yes. Automated error handling checks enforce context wrapping with %w, catch ignored errors, and verify meaningful error messages. This reduces manual review time and ensures consistent error propagation across your Go codebase.

How should I structure Go tests for code review?

Go testing review recommends table-driven tests, benchmarks, and go test strategies for maintainability. Small, testable interfaces improve test coverage and make concurrent code easier to verify.

What Go project layout does code review require?

Code review requires a standard Go project layout with go.mod at the root, .go source files, *_test.go test files, and cmd/, internal/, pkg/ directories. This structure enables consistent analysis across error handling, concurrency, interfaces, and testing patterns.

Does Go code review work with existing linting tools?

Yes. The review integrates with golangci-lint, go test, and testify to enforce coding standards. It combines multiple tools to detect anti-patterns and validate idiomatic Go conventions before merge.