go-style-guide

Review Go code against the Go Style Guide for bugs and maintainability issues.

42|2|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/robbyt/claude-skills --skill go-style-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-style-guide
Source: https://github.com/robbyt/claude-skills/tree/main/plugins/go-style-guide/skills/go-style-guide
Command: npx skills add https://github.com/robbyt/claude-skills --skill go-style-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensures Go code adheres to a comprehensive style guide, catching critical bugs, race conditions, and maintainability issues in Go projects.

Core Features & Use Cases

  • Phase-based review: Scope, analyze, and report on critical and important issues.
  • Reference-driven: Consults pattern references like concurrency and errors guidelines.
  • Balance between safety and pragmatism: Focus on production code avoid panics.

Quick Start

Provide a Go file for review, or paste a snippet, and trigger a style review with this skill.

Frequently Asked Questions about go-style-guide

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

FAQPage Schema
How do I review Go code for race conditions and concurrency bugs?

Go style review identifies race conditions, goroutine lifecycle issues, and mutex misuse by analyzing code against concurrency patterns. The Skill checks for unsafe goroutine management, context handling failures, and synchronization problems that cause production failures.

What Go coding practices should I follow to avoid maintainability issues?

Go style review validates error handling, API design, and testing patterns against established guidelines. It flags critical bugs in exception handling, poorly designed interfaces, and missing test coverage that harm long-term code quality.

Can I use this to review pull requests in my Go project?

Yes. The Skill applies phase-based review to completed work and pull requests, analyzing branches for critical and important issues across concurrency, errors, API design, and testing without requiring code to be merged.

What happens if my Go code has panic statements or unsafe patterns?

The Skill focuses on production code and avoids flagging panics unnecessarily, balancing safety with pragmatism. It prioritizes critical bugs like race conditions and lifecycle errors over low-risk style inconsistencies.

How does the review identify API design problems in Go?

Go style review consults API design reference materials to catch poorly scoped interfaces, inconsistent naming, and patterns that complicate consumption. It validates interfaces against Go conventions for clarity and usability.

What reference materials does the review use to assess code?

The Skill leverages six reference documents covering concurrency, errors, style, API design, testing patterns, and a review checklist. These materials ensure consistent, comprehensive evaluation against Go best practices.