skills.rest
achmf
achmfCOMMUNITY
Explore all skills by this author →
GitHub

caveman-review

Parse pull request diffs and output one-line bug, risk, and style suggestions.

Updated Jun 4, 2026
Search Tags:#automation#code review#feedback#pull request#developer productivity#terse
One-click install
npx skills add https://github.com/achmf/KostaHub --skill caveman-review-achmf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/achmf/KostaHub/tree/main/.agents/skills/caveman-review
Command: npx skills add https://github.com/achmf/KostaHub --skill caveman-review-achmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the noise and fluff often found in code reviews, providing developers with direct, actionable feedback that highlights problems and fixes without unnecessary conversational filler.

Core Features & Use Cases

  • Terse Formatting: Enforces a strict one-line format (Location, Problem, Fix) for all review comments.
  • Severity Categorization: Uses optional prefixes like bug, risk, nit, or question to help developers prioritize their work.
  • Use Case: When reviewing a large pull request, use this Skill to quickly identify critical bugs and minor style issues without overwhelming the author with long-winded explanations.

Quick Start

Invoke the caveman-review skill by asking the AI to review the current pull request diff using the terse caveman format.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I get concise code review feedback for a pull request?▼

Concise code review feedback eliminates noise by enforcing a strict one-line format containing the location, problem, and fix, allowing developers to quickly address issues without reading long explanations.

What is the best way to automate identifying bugs in a large pull request?▼

Automating bug identification involves parsing the pull request diff to detect bugs and risks, then categorizing them with severity prefixes like bug, risk, or nit to help developers prioritize fixes efficiently.

How does the one-line format work for automated code review comments?▼

The one-line format for automated code review comments enforces a strict structure of Location, Problem, and Fix, ensuring feedback remains ultra-compressed and directly actionable for the developer.

Can I categorize the severity of style improvements and bugs in PR feedback?▼

Yes, you can categorize the severity of style improvements and bugs in PR feedback by applying optional prefixes like bug, risk, nit, or question, helping developers prioritize their work effectively.

How do I format pull request diffs for immediate developer implementation?▼

To format pull request diffs for immediate developer implementation, analyze the code changes and output formatted, one-line suggestions that highlight problems and fixes without overwhelming the author.

Related Skills

Explore More Software Engineering Skills→
segersnielssegersniels

Review PR

Analyze pull request diffs to generate prioritized feedback on bugs, style, and security.

Community
Intermediate
chroniicallydiistractedchroniicallydiistracted

review-pr-comments

Resolve unanswered GitHub pull request review threads sequentially with verification.

Community
Advanced
jiroamatojiroamato

pr

Create pull requests from current branches using GitHub templates and validation checks.

Community
Intermediate
pjmageepjmagee
4

caveman-review

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

Community
Intermediate