skills.rest
svssdeva
svssdevaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

caveman-review

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

1|1|Updated Apr 20, 2026
Search Tags:#diff analysis#code review#pull request#developer productivity#actionable feedback#severity labels
One-click install
npx skills add https://github.com/svssdeva/agentic-skills --skill caveman-review-svssdeva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/svssdeva/agentic-skills/tree/main/utils/caveman-review
Command: npx skills add https://github.com/svssdeva/agentic-skills --skill caveman-review-svssdeva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces noisy, verbose pull-request feedback into concise, paste-ready review comments that still preserve actionable signal for fast iteration.

Core Features & Use Cases

  • One-line findings: Produces exactly one line per finding in a consistent format (location + problem + fix).
  • Clear severity signaling: Supports optional prefixes like 🔴 bug, 🟡 risk, 🔵 nit, and ❓ q to quickly convey urgency.
  • Auto-triggered PR reviews: Can be invoked to review diffs and automatically generate comments when reviewing pull requests.

Quick Start

Invoke caveman-review when you want terse, one-line PR feedback by saying to the AI to review the diff using the caveman-review style and output each finding as a single line with location, problem, and a concrete fix.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I make pull request comments less verbose during code review?▼

Pull request comments are condensed into ultra-compressed, one-line findings that preserve actionable signal. Each comment strictly formats output as location, problem, and concrete fix to cut feedback noise while maintaining review quality.

How do I generate one-line code review findings from a diff?▼

Diff review requests generate one-line findings by enforcing a strict format combining location, explicit problem, and concrete fix. This output format drops verbose explanations and keeps only paste-ready reviewer comments for fast iteration.

Can I automatically trigger code review comments when reviewing pull requests?▼

Yes, the code review process can be auto-triggered to review diffs and automatically generate comments. It outputs terse, paste-ready feedback directly onto the pull request without manual formatting effort.

How does ultra-compressed PR feedback improve developer productivity?▼

Ultra-compressed PR feedback improves developer productivity by reducing noisy, verbose pull-request feedback into concise comments. Reviewers receive location-based findings with explicit problems and concrete fixes, enabling faster iteration cycles.

When should I avoid using one-line code review comments?▼

One-line code review comments are not suitable for findings requiring deep architectural explanations or multi-step debugging guidance. The strict one-line-per-finding format focuses on actionable signal, potentially dropping necessary context for complex issues.

Related Skills

Explore More Software Engineering Skills→
hyperlane-xyzhyperlane-xyz
97

inline-pr-comments

Post line-specific inline comments to GitHub pull request diffs.

Official
Intermediate
achmfachmf

caveman-review

Parse pull request diffs and output one-line bug, risk, and style suggestions.

Community
Basic
RDCrystalLabRDCrystalLab

caveman-review

Compress code review feedback into concise actionable comments with locations and fixes.

Official
Intermediate
Chris-MaskeyChris-Maskey

caveman-review

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

Community
Intermediate