skills.rest
AlbertLin821
AlbertLin821COMMUNITY
Explore all skills by this author →
GitHub

caveman-review

Generate compressed severity-prefixed code review comments from pull request diffs.

2|Updated Apr 16, 2026
Search Tags:#automation#code review#pull request#clean code#developer productivity
One-click install
npx skills add https://github.com/AlbertLin821/AIYO_new --skill caveman-review-albertlin821
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/AlbertLin821/AIYO_new/tree/main/.agents/skills/caveman-review
Command: npx skills add https://github.com/AlbertLin821/AIYO_new --skill caveman-review-albertlin821

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes fluff and conversational filler from code reviews, providing developers with direct, actionable feedback that highlights bugs, risks, and improvements in a single line.

Core Features & Use Cases

  • Terse Formatting: Enforces a strict L: problem. fix. structure to keep PR discussions focused.
  • Severity Tagging: Uses clear emoji-based prefixes to distinguish between critical bugs, architectural risks, and minor nits.
  • Use Case: When reviewing a large pull request, use this skill to quickly identify and communicate specific line-level issues without writing lengthy, time-consuming explanations.

Quick Start

Invoke the caveman-review skill to analyze the current pull request diff and generate concise feedback.

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?▼

Generate concise code review comments for a pull request by processing diff inputs to identify line-specific bugs and risks, then outputting direct feedback using a strict severity-prefixed format. This removes conversational filler to maintain high-signal communication.

What is the best way to format automated code review feedback?▼

The best way to format automated code review feedback is using a strict L: problem. fix. structure. This enforces precise line-number referencing and concrete fix suggestions, stripping conversational filler to keep PR discussions focused and actionable.

Does this code review approach distinguish between critical bugs and minor stylistic issues?▼

Yes, this code review approach distinguishes between critical bugs and minor stylistic issues using clear emoji-based severity tagging prefixes. This categorization separates critical bugs, architectural risks, and minor nits within the high-signal communication format.

How do I identify line-specific risks in a large pull request diff?▼

Identify line-specific risks in a large pull request diff by operating directly on the diff input to locate bugs and stylistic improvements. The skill requires precise line-number referencing to communicate specific line-level issues without lengthy explanations.

Can I use this for developer productivity automation without writing lengthy explanations?▼

Yes, you can use this for developer productivity automation without writing lengthy explanations. It strips conversational filler and automatically generates ultra-compressed, actionable feedback to quickly identify and communicate specific line-level issues.

Related Skills

Explore More Software Engineering Skills→
InterfaceX-co-jpInterfaceX-co-jp
304

genshijin-review

Compresses pull request feedback into line-referenced comments with severity tags.

Official
Intermediate
Disaster-TerminatorDisaster-Terminator
5

fetch-reviews

Retrieve and parse code review comments from Sourcery, Copilot, and Qodo.

Community
Intermediate
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced
hairihouhairihou

conventional-comments

Generate code review comments in the Conventional Comments format.

Community
Intermediate