caveman-review

Generates one-line code review comments from PR diffs and content.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/wukangcheng2944/claude-skills --skill caveman-review-wukangcheng2944
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/wukangcheng2944/claude-skills/tree/main/caveman-review
Command: npx skills add https://github.com/wukangcheng2944/claude-skills --skill caveman-review-wukangcheng2944

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces verbose code review feedback to concise, actionable one-line findings that preserve essential context and guidance.

Core Features & Use Cases

  • Produces one-line findings with location, problem, and fix for each change.
  • Enforces formatting rules for severity prefixes and drop rules to keep reviews focused.
  • Use Case: when reviewing a PR with multiple files, run caveman-review to generate tight, easily sharable feedback.

Quick Start

Input a pull request diff and output a set of one-line, actionable review comments.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I generate concise code review comments from a pull request diff?

To generate concise code review comments from a pull request diff, input the PR diff content to automatically produce terse, one-line findings with locations and suggested fixes.

What is the best way to automate code reviews for multi-file diffs?

Automating code reviews for multi-file diffs involves processing the PR content to output structured, ready-to-paste comments with severity prefixes, locations, and actionable fixes.

Can I enforce coding style and severity rules in automated review comments?

Yes, you can enforce coding style and severity rules by applying predefined formatting guidelines that generate focused review comments with severity prefixes and no narrative.

Does automated code review work for inline changes in a PR?

Automated code review works for inline changes by analyzing the diff content and generating structured findings that pinpoint exact locations and provide suggested fixes.

How do I format pull request review comments to be actionable and short?

To format pull request review comments to be actionable and short, apply strict drop rules and no-narrative guidelines, producing one-line outputs that preserve essential context and guidance.