code-review

Review an existing code change, pull request, commit, or implementation by reconstructing what the changed code actually does and finding concrete mismatches against intended behavior, system contracts, invariants, and codebase structure. Use after implementation or when explicitly asked to review, audit, inspect, or assess code. Default to diff-based review when a change set exists; inspect surrounding code only as needed to understand impact. Report only actionable findings with evidence and consequence. Do not redesign the product, repeat implementation planning, or emit style/nit feedback that automated tooling or existing conventions can handle.