effective-go

Analyze Go code and refactor it to follow Effective Go principles.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/radkomih/claude-code-ext --skill effective-go-radkomih
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: effective-go
Source: https://github.com/radkomih/claude-code-ext/tree/main/plugins/effective-go/skills/effective-go
Command: npx skills add https://github.com/radkomih/claude-code-ext --skill effective-go-radkomih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you analyze and refactor Go code to align with Effective Go principles, reducing common idioms violations and improving maintainability.

Core Features & Use Cases

  • Analyze formatting, naming, and idioms to propose idiomatic refactors.
  • Identify concurrency, error-handling, and interface design anti-patterns.
  • Provide actionable refactoring guidance with concrete examples.

Quick Start

Provide a Go codebase and ask the assistant to refactor it according to Effective Go principles.

Frequently Asked Questions about effective-go

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

FAQPage Schema
How do I refactor Go code to use proper error handling and idiomatic patterns?

Refactoring Go code to apply Effective Go principles involves analyzing your project for anti-patterns and applying idiomatic error-handling improvements, proper receiver usage, and small interface designs to improve maintainability.

What are common concurrency anti-patterns in Go and how do I fix them?

Concurrency anti-patterns in Go are identified by analyzing your codebase for violations of Effective Go principles, which then proposes concurrency-safe refactors to ensure proper synchronization and idiomatic channel usage.

Does this approach check for gofmt compliance and proper receiver usage?

Yes, analyzing Go code with this approach enforces gofmt compliance and validates proper receiver usage, ensuring your project follows Effective Go idioms for formatting and structural consistency.

How do I start refactoring an existing Go codebase for idiomatic formatting?

To refactor an existing Go codebase, provide your code to the analyzer and request refactoring according to Effective Go principles, which yields actionable guidance with concrete examples for formatting and naming.

Why should I use small, focused interfaces instead of large ones in Go?

Small, focused interfaces are a core Effective Go principle that improves maintainability by reducing idioms violations, which this analysis identifies when proposing refactors for interface design anti-patterns.

Can static analysis help identify violations of Effective Go idioms in my project?

Static analysis helps identify Effective Go idioms violations by examining your codebase for formatting, naming, and concurrency issues, providing actionable refactoring guidance with concrete examples to resolve them.