Guide idiomatic Go architecture, error handling, and concurrency design.
npx skills add https://github.com/Muvon/octomind-tap --skill programming-go-muvon
Please help me install this Agent Skill. Skill: programming-go Source: https://github.com/Muvon/octomind-tap/tree/main/skills/programming-go Command: npx skills add https://github.com/Muvon/octomind-tap --skill programming-go-muvon
This Skill helps you design Go codebases that stay readable and maintainable by enforcing idiomatic architecture, safe error handling, and practical concurrency patterns.
Ask the AI to refactor your Go service design to be idiomatic: improve package boundaries, fix error-wrapping and sentinel/typed errors, and revise your concurrency and context usage according to Go best practices.
High-intent search queries and answers about installing and using this skill.
Structure Go packages by capability-driven boundaries like auth or billing rather than layered controllers and services. This idiomatic architecture keeps package boundaries clear and ensures your codebase stays readable and maintainable as the system grows.
Handle errors in Go by treating them as values, wrapping them with %w for proper error chains, and using typed or sentinel error patterns. This approach allows callers to inspect errors reliably using standard library functions like errors.Is and errors.As.
Prevent goroutine leaks and race conditions by enforcing disciplined goroutine lifecycle management, using context-first I/O for cancellation, and establishing clear channel ownership semantics. This ensures safe parallel work without leaking resources or creating data races.
You should use the Go standard library first, utilizing net/http, encoding/json, and log/slog before pulling in external frameworks. This standard-library-first approach keeps dependencies minimal and aligns with idiomatic Go architecture.
Refactor an existing Go service by asking the AI to improve package boundaries, fix error-wrapping with %w, implement sentinel or typed errors, and revise concurrency and context usage according to Go best practices.
Race conditions in Go often occur due to unclear channel ownership semantics and undisciplined goroutine lifecycles. Fix them by establishing strict channel ownership rules, using context-first I/O for cancellation, and managing goroutine lifecycles to avoid concurrent access issues.
lowranceworksProvides idiomatic guidance and best practices for writing, debugging, and maintaining Go applications.
saifoellohAnalyze Go code for race conditions, deadlocks, and goroutine leaks.
JamesPrialDetect goroutine leaks and implement clean exit patterns.
Jonathan0823Codify Go idioms, error handling, concurrency patterns, and clean architecture for backend code.
