Guides Go code design with explicit error handling, concurrency discipline, and narrow interfaces.
npx skills add https://github.com/astroville/sprout --skill go-stack-astroville
Please help me install this Agent Skill. Skill: go-stack Source: https://github.com/astroville/sprout/tree/main/.claude/skills/go-stack Command: npx skills add https://github.com/astroville/sprout --skill go-stack-astroville
context usage for cancellation and deadlines while flagging goroutine leaks, data races, blocking behavior, and retry mistakes. - Use Case: When implementing a new Go service or reviewing a pull request, apply this guidance to decide whether an interface is justified, whether concurrency actually helps, and whether errors are handled explicitly. ## Quick Start Review my Go package for interface overuse, goroutine leaks, and missing context propagation using the go-stack guidance.High-intent search queries and answers about installing and using this skill.
Keep packages small with a single clear responsibility, and avoid splitting code by technical layer alone. Add interfaces only when a real substitution need exists, not as a default design step.
Handle errors explicitly at each call site with direct control flow rather than hiding them behind abstractions. Return errors to the caller who can act on them, and keep the handling path easy to trace.
Add concurrency only where it clearly helps, such as parallel I/O or independent work units. Always pair goroutines with context-based cancellation and deadlines so they terminate predictably.
Ensure every goroutine has a defined exit path, typically via context cancellation or closed channels. Protect shared state with clear ownership or synchronization, and watch for blocking sends and unbounded retries.
Interface-first design is a mistake when there is no real substitution need, such as multiple implementations or test doubles. Prefer concrete types first and extract narrow interfaces only when a consumer requires them.
arvindbattulaDefine stable API contracts for REST endpoints and TypeScript interfaces before implementation.
PeterBookerRun go vet, golangci-lint, and go tests with the race detector.
carayaReview Go packages for API design, concurrency safety, and error handling.
hector-mannyExplain idiomatic Rust patterns for ownership, error handling, traits, and concurrency.