go-error-patterns

Installation
SKILL.md

Go error patterns

Use this skill when a Go task is really about error-type design, shared helper signatures, or architecture boundaries around Go services and lambdas, and the next step is to normalize types instead of treating the problem as a generic build failure.

Use this skill when

  • A shared helper expects func(string) error, but the available constructor returns a concrete error pointer type.
  • Someone assumes Go function types are covariant and expects func(string) *DomainError to satisfy func(string) error.
  • The design uses package-local type aliases for shared helper or DTO types and needs to be normalized.
  • A Go signature needs a decision between returning error and returning a concrete pointer type.
  • A Go architecture question touches lambda or binary granularity for separate product areas or categories.

Do not use this skill when

  • The immediate problem is a failing go build, go test, govulncheck, or CI parity issue.
  • The real need is runtime input validation or schema typing at an API boundary.
  • The cause is still completely unknown and needs language-agnostic debugging before any design choice is made.

Routing boundary

Installs
6
GitHub Stars
4
First Seen
Jun 20, 2026