agentsclimarketplace

Golang error handling

Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/golang-error-handling

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install
npx -y skills add ComeOnOliver/skillshub --skill golang-error-handling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Standards for error wrapping, checking, and definition in Golang. Use when wrapping errors, defining sentinel errors, or handling errors idiomatically in Go. (triggers: fmt.Errorf, errors.Is, errors.As, error wrapping, sentinel error, error handling)

SKILL.md

1.3 KB, as published. Nobody here has run it

Golang Error Handling Standards

Priority: P0 (CRITICAL)

Principles

  • Errors are Values: Handle them like any other value.
  • Handle Once: Log OR Return. Never Log AND Return (creates duplicate logs).
  • Add Context: Don't just return err bubble up. Wrap it with context: fmt.Errorf("failed to open file: %w", err).
  • Use Standard Lib: Go 1.13+ errors package (Is, As, Unwrap) is sufficient. Avoid pkg/errors (deprecated).

Guidelines

  • Sentinel Errors: Expoted, fixed errors (io.EOF, sql.ErrNoRows). Use errors.Is(err, io.EOF).
  • Error Types: Structs implementing error. Use errors.As(err, &target).
  • Panic: Only for unrecoverable startup errors.

Anti-Patterns

  • No bare return err: Wrap with fmt.Errorf("context: %w", err) to preserve call chain.
  • No string error checks: Use errors.Is/errors.As; string comparison is brittle.
  • No swallowed errors: Never assign errors to _; always handle or propagate.

References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.