review-go-backlog-implementation

Provide the backlog issue, any implementation spec, and the code changes. The review maps each acceptance criterion to code and test evidence, inspects failure paths, and reports severity-ranked findings with file and line references.

It checks error wrapping with %w, context handling, resource cleanup on all paths, mutex and goroutine ownership, malformed-input safety, and recovery behavior after crashes or retries. Passing tests are treated as evidence, not proof of correctness.

Yes, it runs narrow checks first such as go test and go vet on changed packages, then broader checks like golangci-lint when the environment permits. It reports exactly which commands ran and distinguishes environmental failures from implementation defects.

No, it never edits source files, backlog artifacts, or specifications unless explicitly asked. It only reports actionable findings with remediation direction and preserves unrelated working-tree changes.

Findings use P0 for data loss or safety violations, P1 for significant correctness or contract failures, P2 for bounded defects with operational cost, and P3 for low-risk actionable improvements.