agentleFS
testdino-hqtestdino-hq/google-styleguides-skills/go/SKILL.md

go

Skill15 starsChanged 9 months agoMITView on GitHub

Google's official Go style guide. Covers gofmt formatting, naming conventions, error handling, interfaces, concurrency patterns, and package organization. Enforces idiomatic Go code with short variable names and explicit error checks.

The file

Files
SKILL.md

Google Go Style Guide

Official Google Go coding standards for idiomatic, maintainable code.

Golden Rules

  1. Run gofmt before commit — formatting is non-negotiable
  2. Short variable names in small scopes — i, err, ctx
  3. Error handling, not exceptions — check every error
  4. Interfaces for abstraction — accept interfaces, return structs
  5. Defer for cleanup — ensure resources are released
  6. Explicit is better — avoid magic, prefer clarity
  7. Package names: lowercase, single word — no underscores

Quick Reference

Naming Conventions

ElementConventionExample
Packageslowercasepackage user
Fileslowercase_underscoreuser_service.go
TypesUpperCamelCaseUserService
Functions/MethodsUpperCamelCase (exported)GetUser
Functions/MethodslowerCamelCase (unexported)getUserByID
VariableslowerCamelCaseuserCount
ConstantsUpperCamelCase or UPPER_SNAKEMaxRetries
InterfacesUpperCamelCase + -er suffixReader, Writer

Variables

// ✓ CORRECT - short names in small scopes
for i := 0; i < 10; i++ {
    // ...
}

// ✓ CORRECT - descriptive names in larger scopes
func ProcessUserData(userRepository UserRepository) error {
    // ...
}

// ✗ INCORRECT - unnecessarily long
for index := 0; index < 10; index++ {
    // ...
}

Error Handling

// ✓ CORRECT - check every error
user, err := getUser(id)
if err != nil {
    return nil, fmt.Errorf("failed to get user: %w", err)
}

// ✗ INCORRECT - ignoring errors
user, _ := getUser(id)

Functions

// ✓ CORRECT - multiple return values
func GetUser(id int) (*User, error) {
    // ...
}

// ✓ CORRECT - named return values for clarity
func ParseConfig(path string) (cfg *Config, err error) {
    // ...
}

Interfaces

// ✓ CORRECT - small, focused interfaces
type Reader interface {
    Read(p []byte) (n int, err error)
}

// ✓ CORRECT - accept interfaces, return structs
func ProcessData(r Reader) (*Result, error) {
    // ...
}

Defer

// ✓ CORRECT - defer for cleanup
func ReadFile(path string) ([]byte, error) {
    f, err := os.Open(path)
    if err != nil {
        return nil, err
    }
    defer f.Close()
    
    return io.ReadAll(f)
}

Goroutines and Channels

// ✓ CORRECT - use context for cancellation
func ProcessItems(ctx context.Context, items []Item) error {
    for _, item := range items {
        select {
        case <-ctx.Done():
            return ctx.Err()
        default:
            if err := process(item); err != nil {
                return err
            }
        }
    }
    return nil
}

// ✓ CORRECT - buffered channels when appropriate
results := make(chan Result, len(items))

Package Organization

// ✓ CORRECT - package comment
// Package user provides user management functionality.
package user

// ✓ CORRECT - group imports
import (
    "context"
    "fmt"
    
    "github.com/pkg/errors"
    
    "myapp/internal/db"
)

Common Mistakes

MistakeCorrect Approach
Ignoring errorsCheck every error
Long variable names in loopsUse short names (i, j)
Panic for normal errorsReturn errors
Naked returnsUse explicit returns
Not running gofmtAlways format code
Underscores in package namesUse single lowercase word

When to Use This Guide

  • Writing new Go code
  • Refactoring existing Go
  • Code reviews
  • Setting up linting rules (golangci-lint)
  • Onboarding new team members

Install

npx skills add testdino-hq/google-styleguides-skills/go

Full Guide

See go.md for complete details, examples, and edge cases.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.