caveman-review

Code review comments for a pull request can be generated as ultra-compact, one-line statements. Each output includes exact line references, the identified problem, and the suggested fix, ready to paste into the PR conversation.

Reviewing multi-file PR diffs without noise requires compressing feedback into terse, one-line comments. This format preserves the actionable signal and maintains exact file and line identifiers to accelerate reviewer velocity across the diff.

Formatting pull request feedback as actionable statements involves structuring each comment on a single line: location, problem, and fix. Optional severity prefixes can be added to indicate the importance of each defect or improvement.

One-line review comments with exact line numbers are supported for code diffs. The generated feedback maintains precise line references across multiple files, ensuring each terse statement accurately pinpoints the location requiring attention.

This code review tool supports optional severity prefixes for pull request comments. These prefixes help categorize the urgency of defects and improvements within the one-line, location-specific feedback format.

Ultra-compact one-line code reviews should be avoided when a defect requires extensive explanation or architectural context. This approach is designed for quick, terse feedback, cutting noise while preserving actionable signal, not detailed conversational debate.