Skill

effective-go

Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.

Install

npx claudepluginhub linehaul-ai/linehaulai-claude-marketplace --plugin golang-orchestrator

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Apply best practices and conventions from the official [Effective Go guide](https://go.dev/doc/effective_go) to write clean, idiomatic Go code.

Supporting Assets

references/error-handling.md

SKILL.md

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

159.9k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

159.9k

MCP Integration

6 files

Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.

plugin-dev

83.2k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitFeb 8, 2026

Actions

View Source View Plugin View on GitHub View README

Effective Go

Apply best practices and conventions from the official Effective Go guide to write clean, idiomatic Go code.

When to Apply

Use this skill automatically when:

Writing new Go code

Reviewing Go code

Refactoring existing Go implementations

Key Reminders

Follow the conventions and patterns documented at https://go.dev/doc/effective_go, with particular attention to:

Formatting: Always use gofmt - this is non-negotiable

Naming: No underscores, use MixedCaps for exported names, mixedCaps for unexported

Error handling: Always check errors; return them, don't panic

Concurrency: Share memory by communicating (use channels)

Interfaces: Keep small (1-3 methods ideal); accept interfaces, return concrete types

Documentation: Document all exported symbols, starting with the symbol name

References

Official Guide: https://go.dev/doc/effective_go

Code Review Comments: https://go.dev/wiki/CodeReviewComments

Standard Library: Use as reference for idiomatic patterns

Error Handling Reference: See references/error-handling.md for comprehensive error handling patterns (wrapping, sentinel errors, custom types, testing)