testdino-hq/google-styleguides-skills

go

Google's official Go style guide.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/testdino-hq/google-styleguides-skills --skill go

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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

go
// ✓ 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

go
// ✓ 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

go
// ✓ 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

go
// ✓ 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

go
// ✓ 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

go
// ✓ 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

go
// ✓ 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

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

Full Guide

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

按任务相关推荐