skills.rest
giovannimnz
giovannimnzCOMMUNITY
Explore all skills by this author →
GitHub

caveman-review

Generate one-line code-review comments for PR diffs with severity prefixes and line numbers.

Updated Apr 23, 2026
Search Tags:#formatting#diff#code-review#pull-request#terse#caveman-review
One-click install
npx skills add https://github.com/giovannimnz/gsd-caveman-hermes --skill caveman-review-giovannimnz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/giovannimnz/gsd-caveman-hermes/tree/main/skills/caveman-review
Command: npx skills add https://github.com/giovannimnz/gsd-caveman-hermes --skill caveman-review-giovannimnz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-compressed code review comments cut noise from PR feedback while preserving actionable signal. Each comment is one line: location, problem, fix. Use when reviewing pull requests or invoking /caveman-review.

Core Features & Use Cases

  • One-line, actionable feedback per finding with exact line or file references.
  • Enforces a fixed format for consistency and faster review cycles.
  • Useful for rapid PR reviews, automated lint-like checks on diffs, and team-wide standards.

Quick Start

Provide a terse, one-line code-review comment for each finding in the diff.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I generate terse one-line code-review comments for pull request diffs?▼

To generate terse one-line code-review comments, apply a strict formatting structure to pull request diffs that preserves location, problem, and fix. This enforces non-verbose feedback with severity prefixes and exact line numbers.

What is the best way to reduce noise in automated PR code reviews?▼

The best way to reduce noise in automated PR code reviews is to compress feedback into ultra-terse, one-line comments. Dropping non-actionable phrases ensures each finding retains only the necessary signal.

Can I apply strict formatting guidelines to multi-file pull request diffs?▼

Yes, you can apply strict formatting guidelines to multi-file pull request diffs. The review process identifies findings across all files and enforces a fixed format with severity prefixes and exact line references.

How do I invoke automated code reviews using the /caveman-review command?▼

You can invoke automated code reviews by triggering the /caveman-review command on a pull request. This auto-trigger generates ultra-terse, one-line feedback for each finding in the diff.

Does this code review tool work without external dependencies?▼

Yes, this code review tool works without external dependencies. It operates standalone to parse pull request diffs and output compressed, actionable feedback with exact line numbers and severity prefixes.

What are the limitations of using ultra-terse one-line code review comments?▼

The limitation of ultra-terse one-line code review comments is the strict non-verbose structure, which drops non-actionable phrases. This format prioritizes rapid feedback and may omit broader explanatory context for complex issues.

Related Skills

Explore More Software Engineering Skills→
PacificStudioPacificStudio
264

review-code

Review code changes for risks with prioritized findings and file references.

Official
Intermediate
ybbms777ybbms777
1

resolve-pr-feedback

Process GitHub pull request review feedback end-to-end with gh and jq.

Community
Advanced
rvdbreemenrvdbreemen
199

caveman-review

Generate one-line code review comments with line numbers and fixes.

Community
Basic
Chris-MaskeyChris-Maskey

caveman-review

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

Community
Intermediate