skills.rest
xaionaro
xaionaroCOMMUNITY
Explore all skills by this author →
GitHub

caveman-review

Generate one-line code review findings for pull request diffs.

Updated May 4, 2026
Search Tags:#automation#diff#code-review#pull-request#one-line#caveman-review#comment-format
One-click install
npx skills add https://github.com/xaionaro/.config-codex --skill caveman-review-xaionaro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/xaionaro/.config-codex/tree/main/skills/caveman-review
Command: npx skills add https://github.com/xaionaro/.config-codex --skill caveman-review-xaionaro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

Core Features & Use Cases

Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing. Format: L<line>: <problem>. <fix>. — or <file>:L<line>: ... when reviewing multi-file diffs. Drop and Keep rules ensure concise feedback with consistent style.

Quick Start

Use caveman-review to generate terse one-line findings for a PR.

Frequently Asked Questions about caveman-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate concise code review comments for a pull request diff?▼

To automate concise code review for a pull request, this skill produces one-line findings for PR diffs. It outputs exact line references, token names in backticks, and concrete fixes without unnecessary explanation.

What is the format for ultra-brief code review comments on a multi-file diff?▼

The format for ultra-brief code review comments is a single line per finding: L<line>: <problem>. <fix>. for single files, or <file>:L<line>: ... when reviewing multi-file diffs to ensure consistent, actionable feedback.

How do I get actionable code review feedback without the noise on my PR?▼

To get actionable code review feedback without noise, this skill cuts throat-clearing and preserves only the signal. Each comment contains the location, problem, and fix in one line, dropping anything non-essential.

Can I trigger an automated code review by invoking a command on a pull request?▼

You can trigger an automated code review by invoking /caveman-review or saying "review this PR". It auto-triggers when reviewing pull requests and processes the diff to generate terse one-line findings.

Does this automated code review tool work with multi-file diffs?▼

Yes, this automated code review tool works with multi-file diffs. It adjusts the output format to include the file name and exact line reference, ensuring every finding remains a single, actionable line.

Related Skills

Explore More Software Engineering Skills→
huangzidahuangzida
2

caveman-review

Generate terse one-line code review comments for pull request diffs.

Community
Intermediate
mdmagnuson-creatormdmagnuson-creator

merge-conflicts

Merge target branches into source branches and resolve pull request conflicts.

Community
Advanced
man-groupman-group
2.5k

review-pr

Review ArcticDB pull requests and post deduplicated inline comments.

Official
Advanced
Chris-MaskeyChris-Maskey

caveman-review

Compress pull request review findings into one-line comments with location, problem, and fix.

Community
Intermediate