code-review

Resource leak detection flags patterns where Get() callers return a closer that must be closed. Ensure proper deferral of Close() to prevent leaked resources that can degrade performance or cause failures in Pebble applications.

Enforce per-goroutine iterators and safe lock handling to avoid race conditions. Each goroutine must have its own iterator instance, and locks must be held consistently to prevent concurrent access that corrupts data.

Apply a standardized review checklist covering resource management, iterator safety, lint compliance, and concurrency patterns. This accelerates code reviews and maintains Pebble's quality bar by catching correctness issues early.

Iterator misuse occurs when code accesses Key or Value before proper positioning, or fails to verify iteration errors via Error() after loops. Correct positioning and error checking prevent panics and data corruption in Pebble operations.

Yes, this review process applies to code diffs, pull requests, and changes requested by maintainers across the Pebble codebase. It codifies patterns for resource management and iterator safety to surface issues during any review workflow.