skills.rest
austinwilcox
austinwilcoxCOMMUNITY
Explore all skills by this author →
Website𝕏@Seconds21iveGitHub

caveman-review

Generate one-line code review comments with locations and fixes for PR diffs.

1|1|Updated Jul 31, 2023
Search Tags:#diff analysis#code review#pull request#format enforcement#actionable feedback#one-line comments#severity tagging
One-click install
npx skills add https://github.com/austinwilcox/dotfiles --skill caveman-review-austinwilcox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/austinwilcox/dotfiles/tree/main/.claude/skills/caveman-review
Command: npx skills add https://github.com/austinwilcox/dotfiles --skill caveman-review-austinwilcox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Caveman-review removes noisy, verbose feedback from pull request reviews so you can deliver one-line, paste-ready findings that preserve actionable signal.

Core Features & Use Cases

  • Ultra-compressed one-line findings: Produces a single line per finding in a consistent format (location + problem + fix).
  • PR-focused operational style: Optimized for situations where the user asks for review (e.g., “review this PR”, “code review”, “/review”, or “/caveman-review”), including auto-triggering during pull request reviews.
  • Optional severity tagging: Supports concise prefixes for different severities (🔴 bug, 🟡 risk, 🔵 nit, ❓ q) to help prioritize.

Quick Start

Ask for caveman-review by saying “/caveman-review: review this PR” and provide the diff so it can return one line per finding using the required format.

Frequently Asked Questions about caveman-review

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

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

To get concise code review comments, use a tool that generates ultra-compressed, one-line findings per issue. This approach enforces strict formatting by dropping filler phrasing and outputting only the exact location, problem, and concrete fix for each finding in your pull request diff.

What is the best way to format actionable feedback for a multi-file diff review?▼

The best way to format actionable feedback for a multi-file diff is a single line per finding containing the exact location, problem, and fix. This strict format eliminates noisy, verbose explanations and ensures paste-ready review feedback with optional severity prefixes like bug or risk.

Can I prioritize code review findings using severity tagging?▼

Yes, you can prioritize code review findings using optional severity prefixes. You can tag issues as a bug, a risk, a nit, or a question, which helps developers quickly identify the most critical problems and apply the necessary concrete fixes in order of importance.

How do I trigger an automated PR review with one-line comments?▼

You can trigger an automated PR review by using specific request phrases like code review, review this PR, /review, or /caveman-review. Providing the diff alongside these triggers prompts the system to analyze the changes and return one-line, paste-ready findings.

Does ultra-terse code review drop explanatory context from pull request feedback?▼

Yes, an ultra-terse code review drops explanatory context by enforcing strict formatting rules that remove filler phrasing. It preserves actionable signal by strictly limiting output to the exact location, the specific problem, and the concrete fix required.

Related Skills

Explore More Software Engineering Skills→
HillBombCreationsHillBombCreations

cmd-reviewer

Automate code review analysis across local changes, branches, and pull request diffs.

Official
Advanced
daodaoedudaodaoedu

code-review

Review branch diffs and produce a severity-tagged findings table.

Official
Intermediate
g-lokg-lok
1

caveman-review

Generate one-line code-review comments from pull request diffs.

Community
Intermediate
Chris-MaskeyChris-Maskey

caveman-review

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

Community
Intermediate