caveman-review

Generate one-line code review comments with location, problem, and fix for pull requests and diffs.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/venomez-viper/PathWise --skill caveman-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/venomez-viper/PathWise/tree/main/.agents/skills/caveman-review
Command: npx skills add https://github.com/venomez-viper/PathWise --skill caveman-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-compressed code review comments that cut noise from PR feedback while preserving the actionable signal. Each comment is one line containing the location, the problem, and the fix.

Core Features & Use Cases

  • One-line findings per issue with precise line references.
  • Enforces a consistent format: location, problem, fix, and optional severity prefixes.
  • Ideal for PR reviews and diffs to accelerate feedback with minimal noise.

Quick Start

Review the current PR with caveman-review to generate terse, actionable feedback for each finding.

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 for a pull request diff?

To generate concise code review comments, apply the skill to a pull request diff. It outputs ultra-compressed, one-line feedback per issue containing the exact line location, problem, and fix.

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

The best way to reduce noise in PR review feedback is to enforce a consistent format that omits filler. It outputs only the location, problem, and concrete fix with optional severity prefixes.

Can I get line-specific actionable fixes from an automated code review?

Yes, you can get line-specific actionable fixes. The process identifies exact line references within a diff and provides a concrete fix for each problem while preserving code identifiers in backticks.

Does this automated code review format work without additional dependencies?

Yes, this automated code review format works without additional dependencies. It requires no external components to parse diffs and generate terse, actionable feedback with precise line references.

What format do automated code review comments follow for pull requests?

Automated code review comments follow a strict one-line format: location, problem, and fix. They include optional severity prefixes and wrap all code identifiers in backticks for clear readability.