What problem does it solve?
This Skill helps teams prevent common and costly Go engineering issues by enforcing architectural rules, consistent style, and concurrency-safe patterns during audits, refactors, and reviews.
Core Features & Use Cases
- Architecture guardrails: Enforces NO pkg/, encourages a flat-by-default structure, and promotes standard Go project layout (with
internal/ and cmd/ usage).
- Style and quality enforcement: Directs users to check style_cheatsheet.md first and apply senior-grade feedback using senior_review_checklist.md.
- Concurrency safety: Requires goroutine lifecycle clarity (Context, WaitGroup) and recommends
errgroup for parallel work.
- Workflow for actionability: Provides stepwise guidance for audit, refactor, and review, plus domain-specific references for HTTP services, advanced testing, linting, Ebitengine, and Go idioms.
- Use cases: Ideal for “audit and fix” requests on existing Go repos, preparing PRs for senior review, or refactoring code to remove architectural violations like a disallowed
pkg/ directory.
Quick Start
Use the go-best-practices skill to review a Go repository for disallowed architecture patterns and concurrency risks.