caveman-review

To generate concise code review comments, process the pull request diff to output one line per finding. This format maps each finding to an exact line location, tags it by severity, and proposes a concrete fix.

Yes, pull request feedback can be formatted to include exact line numbers and severity levels. The output strictly follows a single-line format per finding, using severity prefixes like bug, risk, nit, or question for quick triage.

Automating noise-free diff analysis requires dropping hedging language and restating of the diff. The analysis produces ultra-compressed feedback that clearly states the location, the problem, and the concrete fix without unnecessary text.

To add context to security issues in code review feedback, expand the single-line format with an optional rationale. This provides the necessary architectural and security context for complex findings while keeping other comments scannable.

No dependencies are required to run lintless code review on a diff. You can trigger the review directly by asking the assistant to review the diff or by invoking the command interface.

Using a one-line-per-finding format for pull request code reviews eliminates noisy, verbose comments. This ultra-compressed approach keeps reviews scannable and helps authors triage feedback quickly using severity prefixes.