What problem does it solve? Code review comments often bury the actual finding under hedging, filler phrases, and restatements of the diff, slowing down both reviewers and PR authors. This Skill produces terse, actionable review comments that state the location, problem, and fix in a single line. ## Core Features & Use Cases - One-line findings: Outputs comments in the format L<line>: <severity> <problem>. <fix>. with exact line numbers and backticked symbol names. - Severity tagging: Classifies findings as bug, risk, nit, or question using emoji prefixes so authors can triage quickly. - Auto-clarity mode: Automatically switches to full explanations for security findings, architectural disagreements, and onboarding contexts, then resumes terse output. - Use Case: Paste a pull request diff and ask for a review; receive paste-ready comments like L42: bug: user can be null after .find(). Add guard before .email. ## Quick Start Ask the assistant to review this PR diff using caveman-review and output one-line comments for each finding.
