go-style

Enforce Go style consistency using canonical reference documents and rules.

16|3|Updated May 5, 2026
One-click install
npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill go-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-style
Source: https://github.com/Kevin-Liu-01/Agent-Machines/tree/main/knowledge/skills/go-style
Command: npx skills add https://github.com/Kevin-Liu-01/Agent-Machines --skill go-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a complete reference for Go style decisions, conventions, and best practices to ensure consistent, high-quality Go code across projects.

Core Features & Use Cases

  • Full-reference documents: Guide, Decisions, and Best Practices for Go style.
  • Quick decision guidance: referencing the canonical principles and patterns for naming, imports, documentation, and testing.
  • Use Case: You are reviewing or authoring Go code and need authoritative style guidance to justify design choices.

Quick Start

Read the Go Style — Full Reference and consult the Guide, Decisions, and Best Practices documents before making any style judgments.

Frequently Asked Questions about go-style

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

FAQPage Schema
What are the best practices for Go code review and naming conventions?

Go code review best practices involve checking formatting, naming, imports, and documentation against a standardized decision framework. This reference loads canonical rules from .agents/rules/go.md to guide consistent style judgments across projects.

How do I enforce Go style consistency across multiple codebases?

To enforce Go style consistency, consult a complete style guide covering decisions, best practices, and testing conventions. This ensures standardized formatting and naming across all refactoring and code review tasks.

Does this Go style reference work without external dependencies?

Yes, this Go style reference operates without external dependencies. It provides self-contained guide, decisions, and best practices documents to enforce coding conventions directly during your code reviews.

What is the canonical way to structure imports in Go?

Canonical Go import structure is determined by consulting the style decisions and best practices documents. This framework provides authoritative guidance to justify your import ordering and grouping choices during code reviews.

Can I use this reference to standardize Go testing conventions?

Yes, you can use this reference to standardize Go testing conventions. It includes full-reference documents that guide testing decisions and documentation standards to ensure consistent, high-quality code across projects.

How do I justify Go refactoring choices during a code review?

You justify Go refactoring choices by referencing the canonical principles and patterns provided in the style guide. This decision framework applies standardized rules for naming, imports, and documentation to validate design choices.