菜单
Use samber/oops for structured Go errors with wrapping, codes, context attributes, public messages, stack traces, and panic recovery.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/matdev83/golang-curated-agent-skills --skill golang-samber-oops命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Go benchmark and profile workflow: b.Loop, benchstat, pprof, trace, compiler diagnostics, and regression gates.
Go command-line applications: choose a framework, build commands and flags, layer configuration, handle output and exit status, support signals and completion, and test behavior.
Practical Go style for readable, idiomatic code: formatting, control flow, declarations, API boundaries, comments, zero values, and reviewable organization. Use when writing or reviewing Go code where clarity matters beyond gofmt.
正在显示 SKILL.md
| name | golang-samber-oops |
| description | Use samber/oops for structured Go errors with wrapping, codes, context attributes, public messages, stack traces, and panic recovery. |
This guidance targets github.com/samber/oops v1.23. oops errors implement error and preserve an underlying cause through Unwrap. It complements, rather than replaces, ordinary errors.Is/As and deliberate public error mapping.
The builder is immutable-style and materializes an error at terminal methods:
func CreateUser(ctx context.Context, id string) (err error) {
if err := validateID(id); err != nil {
return oops.Code("validation").With("user_id", id).Wrap(err)
}
return oops.In("users").
WithContext(ctx, "request_id").
Code("create_failed").
Public("Unable to create the user").
Wrap(save(ctx, id))
}
Use With with key/value pairs and keep secrets/large payloads out of attributes. Use Code for machine classification, In for a domain, Trace/Span for correlation, and Public for a user-safe message. Attributes improve logs and diagnostics; they are not a license to record personal data.
Use oops.Wrap or a builder's Wrap for a causal error. Do not replace a sentinel or typed cause if callers need errors.Is/As. Map an internal oops error to a transport status in the boundary; percent-v formatting does not sanitize or establish an API security boundary.
Recover and Recoverf accept a callback with no return values and return an error:
func runSafely() (err error) {
return oops.Code("panic_recovered").Recover(func() {
work()
})
}
Use recovery at a process/request boundary where the policy is to convert a panic. Do not wrap every function or continue after an invariant panic without understanding state corruption. Ensure the callback captures the intended values; there is no implicit variable named r.
Use oops.AsOops(err) according to the installed API, or errors.As when the concrete target is appropriate. OopsError exposes Code, Public, Context, Stacktrace, Sources, and LogValue-style data in current releases. Check the exact accessor signatures before writing adapters.
Log detailed diagnostics once at the ownership boundary. Return/wrap lower-level errors with operation context. Redact attributes, request/response bodies, authorization data, and identifiers according to the application's privacy policy. Test cause identity, code/public fields, nested wrapping, recovery, and serialization if the error crosses a wire.