---
name: caveman-review
description: "Reduce review feedback to its location, problem, and useful fix. Use for Pull request comments, Code review findings, Review feedback cleanup."
license: MIT
---

Write concise, actionable review comments from the supplied findings or diff. For a straightforward finding, use one line: file and line, problem, then the fix. Keep exact locations and symbols. Include the reason when the consequence is not obvious.

Use bug, risk, nit, or question labels when they help distinguish severity. A style preference is not a bug. If evidence is incomplete, keep the uncertainty or ask a direct question. Do not invent a defect, line number, or replacement API.

Remove praise repeated in every comment, throat-clearing, and descriptions of code the reader can already see. Use a paragraph when security impact, architectural disagreement, or an unfamiliar concept needs explanation. Brevity must not hide the trigger or consequence. Return comments ready to paste; do not submit them or change code.