go

Enforce Google's Go Style Guide across Go packages with gofmt formatting.

11|2|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill go-the-perfect-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go
Source: https://github.com/the-perfect-developer/the-perfect-opencode/tree/main/.opencode/skills/go
Command: npx skills add https://github.com/the-perfect-developer/the-perfect-opencode --skill go-the-perfect-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

I help ensure Go code adheres to Google's Go Style Guide, promoting clarity and maintainability.

Core Features & Use Cases

  • Enforces formatting with gofmt, naming conventions (MixedCaps/mixedCaps), and proper initialisms.
  • Standardizes imports, documentation, and error handling to improve readability and consistency.
  • Use Case: When teams refactor Go packages or onboard new contributors, this guide keeps codebase style aligned.

Quick Start

Run gofmt -w . and start applying go style rules across your Go codebase.

Frequently Asked Questions about go

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

FAQPage Schema
How do I enforce Go style and clean code conventions in my projects?

To enforce Go style, apply Google's Go Style Guide rules across your codebase by running gofmt -w . This standardizes formatting, naming conventions, and initialisms to improve code readability and maintainability.

What Go naming and import conventions should I follow for lint-friendly packages?

Go packages should use MixedCaps or mixedCaps for naming, proper initialisms, and standardized import ordering. Following these conventions ensures lint-friendly patterns and robust documentation across new and existing projects.

How do I standardize error handling and documentation when refactoring Golang code?

Standardize Golang error handling and documentation by applying consistent style rules across the project. This ensures codebase alignment and improves readability when teams refactor packages or onboard new contributors.

Does gofmt fix all code readability issues or do I need additional conventions?

While gofmt fixes formatting, additional conventions are needed for comprehensive readability. You must apply rules for naming, imports, documentation, and error handling to fully satisfy Google's Go Style Guide and maintain clean code.

When should I apply Go style guide conventions to my existing codebase?

Apply Go style guide conventions to existing codebases during team refactors or when onboarding new contributors. This keeps codebase style aligned across new and existing packages, promoting long-term clarity and maintainability.