caveman-review

Generate concise code review comments with severity prefixes for pull requests.

8|4|Updated Jul 31, 2025

Search Tags:#code review #pull request #comments #conciseness #actionable feedback

Ready to run

npx skills add https://github.com/aesthezel/venezuela-juega --skill caveman-review-aesthezel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/aesthezel/venezuela-juega/tree/main/.junie/skills/caveman-review
Command: npx skills add https://github.com/aesthezel/venezuela-juega --skill caveman-review-aesthezel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill unit streamlines the code review process by generating ultra-compressed, actionable comments. It eliminates noise from pull request feedback and preserves the essential issues and fixes.

Core Features & Use Cases

Ultra-Compressed Comments: Each comment is a single line detailing the location, problem, and fix.
Custom Severity Levels: Assign severity to comments with prefixes like bug, risk, nit, and q.
Use Case: Use the skill when a PR is reviewed, ensuring that feedback is clear and actionable.

Quick Start

Invoke the caveman-review skill during a code review session to automatically generate concise code comments.

Frequently Asked Questions about caveman-review

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

FAQPage Schema

How do I write concise code review comments for a pull request?▼

To write concise code review comments, generate ultra-compressed feedback detailing the location, problem, and fix in a single line. This approach cuts noise from pull request reviews and preserves essential issues, ensuring your code comments remain clear and actionable.

What is the best way to format actionable feedback for code changes?▼

Actionable feedback is best formatted as a single-line comment that combines the specific location, the exact problem, and the proposed fix. Assigning custom severity levels with prefixes like bug, risk, nit, or q further structures and clarifies the code review feedback.

How do I structure pull request input to generate automated code review comments?▼

To generate automated code review comments, provide structured input mapping specific line numbers to their corresponding comments for each code change. This line-by-line mapping allows the review process to accurately parse changes and produce ultra-compressed, actionable feedback.

Can I assign severity levels to PR review comments?▼

Yes, you can assign severity levels to PR review comments by using specific prefixes such as bug, risk, nit, and q. These custom severity prefixes help categorize the actionable feedback, allowing developers to prioritize fixes during the code review process.

Does this code review approach work without external dependencies?▼

Yes, this code review approach works without external dependencies, utilizing only internal scripts to process the provided structured input. You simply supply the line numbers and code changes to generate ultra-compressed, actionable comments directly within your review session.