Code Review

Use for reviewing a diff or implementation. Identify the intended behavior, inspect callers and changed data paths, then look for reproducible correctness, security and performance defects. Cite the affected file and explain the triggering input and consequence. Prefer high-impact findings over style suggestions. Output prioritized findings with a concrete fix or test, or state what was checked when none are found. Example: trace a missing owner filter to a cross-account read. Do not claim tests ran unless an available tool returned their result.