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.
Works with
--- name: Effective Go description: 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. license: Apache-2.0 --- # Effective Go Apply best practices and conventions from the official [Effective Go guide](https://go.dev/doc/effective_go) 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://github.com/golang/go/wiki/CodeReviewComments - Standard Library: Use as reference for idiomatic patterns
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
