code-review-bugs

Request a fresh-eyes review after writing or modifying code. The review inspects the actual diff, callers, tests, and contracts, traces behavior end to end, then fixes confirmed issues and reports each one with the verification performed.

It catches incorrect error handling, missing validation for empty or malformed inputs, concurrency and ordering problems, dead code, unused parameters, and unnecessary abstractions. It also distinguishes pre-existing defects from regressions introduced by the change.

It fixes every concrete issue found using the smallest safe change that restores a clear invariant, and adds regression tests when the repository has an appropriate test seam. Issues outside safe scope are explicitly noted rather than silently skipped.

Avoid it for speculative feature design or broad refactoring requests, since the review deliberately avoids adding abstractions or large rewrites. It is best suited to verifying a concrete, completed change rather than exploring new architecture.

Focused tests for the changed behavior run first, followed by the broader relevant suite when practical. Diagnostics, lint and type errors, and the final diff are checked, and changed hunks are re-read to catch mistakes introduced by the fixes.