Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing. Rules Format: — or when reviewing multi-file diffs. Severity prefix (optional, when mixed): - — broken behavior, will cause incident - — works but fragile (race, missing null check, swallowed error) - — style, naming, micro-optim. Author can ignore - — genuine question, not a suggestion Drop: - "I noticed that...", "It seems like...", "You might want to consider..." - "This is just a suggestion but..." — use instead - "Great work!", "Looks good overall but..." — say it once at th…