caveman-review

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

Updated Aug 29, 2025
One-click install
npx skills add https://github.com/DDTully/dotfiles --skill caveman-review-ddtully
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/DDTully/dotfiles/tree/main/skills/.agent_skills/caveman-review
Command: npx skills add https://github.com/DDTully/dotfiles --skill caveman-review-ddtully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

Core Features & Use Cases

  • Write terse, actionable one-line review comments.
  • Enforce location, problem, fix format for quick triage.
  • Use cases: during PR review to quickly surface issues without noise.

Quick Start

Provide terse, one-line code-review comments for the current pull request.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I automate terse code review comments on a pull request?

You can automate code review by generating terse one-line comments that pinpoint location, problem, and fix. This Skill processes pull request diffs across single or multiple files, formatting findings with precise line numbers and preserving code identifiers for exact remediation.

What is the best way to reduce noise in PR review feedback?

To reduce noise in PR review feedback, enforce a strict one-line format containing only the location, problem, and fix. This approach cuts unnecessary commentary while preserving the actionable signal needed for quick triage during pull request reviews.

Does this automated code review work on diffs across multiple files?

Yes, automated code review works on diffs from pull requests across single or multiple files in standard codebases. It processes the diff to surface issues with precise line numbers and symbol references without being limited to a single file scope.

How do I format code review findings for quick triage?

Format code review findings as a single line stating the location, problem, and fix. This Skill enforces this structure automatically, preserving exact code identifiers and line numbers so developers can quickly locate and remediate issues in the pull request.

When should I use ultra-compressed comments for code review?

Use ultra-compressed comments during PR review to quickly surface issues without noise. This approach is ideal when you need actionable signal from pull request diffs but want to avoid lengthy explanations that create reading friction during triage.