skills.rest
hamzaPixl
hamzaPixlCOMMUNITY
Explore all skills by this author →
Website𝕏@pixlHamzaGitHub

caveman-review

Generate one-line code review comments with line numbers and severity markers.

2|Updated Mar 16, 2026
Search Tags:#git#code-review#severity#pr-comments#terse#line-numbers
One-click install
npx skills add https://github.com/hamzaPixl/pixl-ai --skill caveman-review-hamzapixl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/caveman-review
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill caveman-review-hamzapixl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews often contain verbose, redundant feedback that wastes time. Reviewers need concise, actionable comments that pinpoint issues and suggest fixes in a single line.

Core Features & Use Cases

  • Ultra-terse formatting: Generates one-line comments with line numbers, problem, and fix.
  • Severity markers: Optional emoji prefixes categorize bugs, risks, nits, and questions.
  • PR integration: Ideal for fast-feedback cycles, pull-request bots, and CI comment automation.

Quick Start

Ask the caveman-review skill to produce concise review comments for the pull request you are examining.

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 one-line PR review comments for a pull request?▼

To generate concise one-line PR review comments, format feedback as L<line>: <severity> <problem>. <fix>. This ultra-terse format includes line numbers, problem description, and suggested fix.

What is the best way to format terse code review feedback with severity markers?▼

Terse code review feedback uses optional emoji severity markers to categorize bugs, risks, nits, and questions. Format output as L<line>: <severity> <problem>. <fix> for prioritized pull request comments.

How do I automate fast-feedback pull request comments in CI?▼

Automate fast-feedback pull request comments in CI by generating ultra-terse one-line review comments. This format is ideal for PR bots and CI comment automation requiring concise, actionable feedback.

Does the caveman-review format require line numbers for code review comments?▼

Yes, the caveman-review format requires line numbers for code review comments. You must provide the line number, problem description, and suggested fix to generate the properly formatted output.

Can I use terse PR comments for large git pull request diff analyses?▼

Terse PR comments are designed for pull request diff analyses where reviewers need concise, prioritized feedback. The one-line format prevents verbose redundancy in large code reviews.

Why use ultra-terse formatting instead of detailed code review comments?▼

Ultra-terse formatting solves the problem of verbose, redundant manual code reviews that waste time. It provides concise, actionable comments that pinpoint issues and suggest fixes in a single line.

Related Skills

Explore More Software Engineering Skills→
OlshanskOlshansk
8

cmd-pr-review-prepare

Generate context-rich git diffs and identify code improvement areas.

Community
Intermediate
dversozadversoza
2

pr-feedback

Fetch, triage, and address GitHub Pull Request feedback and CI failures.

Community
Advanced
lev-oslev-os

ubs-bug-scan

Scan changed or staged files for AST-level bugs with Ultimate Bug Scanner.

Official
Intermediate
giovannimnzgiovannimnz

caveman-review

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

Community
Intermediate