go-best-practices

Analyze Go codebases for SOLID violations and non-idiomatic patterns.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/marquesfelip/agents-and-skills --skill go-best-practices-marquesfelip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go-best-practices
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/go-best-practices
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill go-best-practices-marquesfelip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps Go developers ensure code adheres to SOLID, Clean Code, Clean Architecture, and Effective Go standards by auditing, refactoring guidance, and writing guidance for new code.

Core Features & Use Cases

  • Automated SOLID and idiomatic Go audits with concrete fixes.
  • Refactoring guidance to align packages with Clean Architecture and ports/adapters patterns.
  • Assistance in writing new Go code following Effective Go idioms and naming conventions.
  • Use cases include code reviews, onboarding, and large-scale refactors of Go codebases.

Quick Start

Run the go-best-practices subagent on the target Go package to identify SOLID violations and idiomatic patterns, and return concrete fixes.

Frequently Asked Questions about go-best-practices

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

FAQPage Schema
How do I identify SOLID violations in my Go codebase?

Identifying SOLID violations in a Go codebase involves auditing packages to detect non-idiomatic patterns and returning concrete fixes for code structure and interface design based on Clean Architecture guidelines.

How do I refactor Go packages to align with Clean Architecture?

To refactor Go packages to align with Clean Architecture, apply ports and adapters patterns through guided analysis that enforces SOLID principles and separates domain logic from external dependencies.

What is the best way to ensure new Go code follows Effective Go idioms?

Ensuring new Go code follows Effective Go idioms requires writing assistance that enforces naming conventions, error handling standards, and interface design during development and code reviews.

Can I use automated checks for Go code reviews and onboarding?

Yes, automated checks can be used during Go code reviews and onboarding to audit existing packages for SOLID compliance and idiomatic patterns, providing concrete recommendations to maintain code quality.

Does Go best practices analysis work for large-scale refactors?

Go best practices analysis works for large-scale refactors by evaluating entire packages against Clean Architecture and Effective Go guidelines, delivering concrete fixes for structural violations.