caveman-review

Concise code review comments for a pull request diff are generated in a strict one-line format containing location, severity, problem, and fix. This format removes hedging and praise, keeping attention on concrete issues and actionable fixes.

The standard format for automated PR comments to ensure high signal over noise is a strict one-line structure: location, severity, problem, and fix. This eliminates restatements and hedging, ensuring findings are faster to scan and easier to act on.

Yes, automated code review can find bugs and assign standardized severity labels in changed code. It covers bug hunting, risk spotting, nitpicks, and clarification questions while requiring exact line references for each finding.

Code review comments requiring exact line references without approval text are produced by enforcing an output-only response format. The strict one-line structure of location, severity, problem, and fix ensures findings stay terse without adding linting or approval text.

One-line code review formatting adapts to complex security or architectural concerns by expanding the explanation within the structured format. It stays terse for routine review notes but provides necessary clarity when the context calls for more explanation.

You should avoid using strict one-line formats for pull request comments when you need to perform linting or require approval text, as this approach enforces output-only responses without approval text or linting capabilities.