golang-error-handling

Checking nil interface values in Go requires verifying both the type and value are nil, because an interface holding a nil pointer is not itself nil. This Skill analyzes your code to identify incorrect nil interface checks that cause unexpected behavior.

Go error wrapping loses context when using incorrect formatting verbs instead of the %w directive, which breaks errors.Is and errors.As chains. This Skill detects missing %w usage in your code to ensure proper error wrapping and accurate comparisons.

Context propagation in Go microservices requires passing context.Context through the entire call stack to maintain cancellation and timeout mechanisms. This Skill reviews your code to ensure downstream operations correctly inherit and respect the request context.

Reviewing Go code for error handling best practices involves analyzing error wrapping with %w, context propagation, and nil interface checks. This Skill identifies critical issues that could lead to lost error information and resource leaks during debugging.

Preventing lost error chains in Go requires using the %w directive when wrapping errors with fmt.Errorf to maintain the error sequence. This Skill analyzes your codebase to find instances where error information is lost due to incorrect wrapping.

Yes, you can use this for reviewing complex microservices to verify that outgoing API calls correctly propagate the request context. This ensures cancelled client requests terminate all downstream operations promptly, preventing resource leaks and broken timeouts.