Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports github.com/samber/oops.
Install
KitScout test notes
Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.
Similar tools
rea-tool-design456,653 ★ Audit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and E
code-review323,485 ★ Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does th
codebase-design323,485 ★ Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interfac
domain-modeling323,485 ★ Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLO
implement323,485 ★ Implement a piece of work based on a spec or set of tickets.