code-guidelines-go

Standardize Go coding practices for the pi-go codebase.

122|13|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/dimetron/pi-go --skill code-guidelines-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-guidelines-go
Source: https://github.com/dimetron/pi-go/tree/main/.pi-go/skills/code-guidelines-go
Command: npx skills add https://github.com/dimetron/pi-go --skill code-guidelines-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Go coding guidelines for pi-go provide a centralized standard to ensure idiomatic, safe, and maintainable Go code across the project.

Core Features & Use Cases

  • Enforces Go idioms: naming, error handling, concurrency, and package layout for pi-go modules.
  • Guides testing strategies (table-driven tests, fuzz, benchmarks) and linting practices with golangci-lint v2.
  • Supports onboarding by documenting best practices and code review expectations for contributors.

Quick Start

Read and apply the Go coding guidelines before contributing any Go changes to pi-go, and reference the standards during code reviews.

Frequently Asked Questions about code-guidelines-go

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

FAQPage Schema
What are idiomatic Go coding practices for error handling and package structure?

Idiomatic Go coding practices for error handling and package structure require clear naming, guard clauses, and explicit option-based configuration to ensure consistency and reduce bugs in Go codebases.

How do I write table-driven tests and benchmarks in Go?

Write table-driven tests and benchmarks in Go by applying standardized testing strategies that include fuzz testing and linting practices guided by golangci-lint v2 to maintain code quality and maintainability.

Does this Go coding standard support onboarding for new contributors?

Yes, this Go coding standard supports onboarding by documenting best practices and code review expectations to ensure contributors write safe, maintainable Go code across the project.

What's the best way to enforce Go concurrency and naming conventions in code reviews?

The best way to enforce Go concurrency and naming conventions in code reviews is to reference centralized Go idiomatic guidelines that standardize package layout, error handling, and linting practices.

Why use explicit option-based configuration and guard clauses in Go development?

Use explicit option-based configuration and guard clauses in Go development to reduce bugs, enforce clear documentation, and ensure maintainability across core development tasks within the codebase.