caveman-review

Generates one-line code review comments with location, severity, problem, and fix.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback is often buried under hedging, filler phrases, and restated diff content, making it slow to write and slow to act on. This Skill compresses PR feedback into terse, actionable one-line comments without losing the technical signal. ## Core Features & Use Cases - One-line comment format: Each finding follows L<line>: <severity> <problem>. <fix>. with exact line numbers and backticked symbol names. - Severity tagging: Uses emoji prefixes to classify findings — 🔴 bug, 🟡 risk, 🔵 nit, ❓ question — so authors can triage at a glance. - Auto-clarity mode: Automatically switches to full explanations for CVE-class security findings, architectural disagreements, and onboarding contexts, then resumes terse output. - Use Case: Paste a pull request diff and ask for a review; receive a ready-to-paste list of comments like L42: 🔴 bug: user can be null after .find(). Add guard before .email. ## Quick Start Ask the assistant to review this pull request diff using caveman-review and output one-line comments with severity tags.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I write concise code review comments for a pull request?

Use a one-line format per finding: line number, severity tag, the problem, and a concrete fix. Drop phrases like "I noticed that" or "you might want to consider" and keep exact symbol names in backticks so the author can act immediately.

How to trigger the caveman-review code review skill?

Invoke it with /caveman-review or by saying "review this PR", "code review", or "review the diff". It auto-triggers when reviewing pull requests and outputs comments ready to paste into the PR.

What severity levels does the review comment format support?

Four optional severity prefixes: 🔴 bug for broken behavior, 🟡 risk for fragile code like missing null checks, 🔵 nit for style issues the author can ignore, and ❓ q for genuine questions rather than suggestions.

When does terse code review output switch to full explanations?

Terse mode is dropped for CVE-class security findings, architectural disagreements, and onboarding contexts where the author needs the reasoning. A normal paragraph is written for those findings, then terse output resumes for the rest.

What are the limitations of automated one-line PR review comments?

The skill only outputs review comments — it does not write code fixes, approve or request changes, or run linters. Complex security or design issues still require full prose explanations rather than one-liners.