caveman-review

Generate concise single-line code review comments with severity levels.

2|1|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/istinataFTS/LiftLeagueLegends --skill caveman-review-istinatafts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/istinataFTS/LiftLeagueLegends/tree/main/fitness_tracker/.agents/skills/caveman-review
Command: npx skills add https://github.com/istinataFTS/LiftLeagueLegends --skill caveman-review-istinatafts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of noisy and unactionable code review comments, providing a concise and actionable approach to feedback.

Core Features & Use Cases

  • Concise Feedback: Generates code review comments in a single-line format, focusing on location, problem, and fix.
  • Severity Levels: Offers different severity levels (bug, risk, nit, question) for clear prioritization.
  • Automated Triggering: Triggers automatically when reviewing pull requests or upon specific commands.

Quick Start

Run the /caveman-review command to generate a code review comment for the current pull request.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I automate concise code review comments for pull requests?

You can automate concise code review comments by triggering a command on pull requests, which parses code diffs and generates single-line feedback focusing on location, problem, and fix.

How do I reduce noisy pull request feedback and focus on actionable fixes?

Reduce noisy pull request feedback by applying predefined severity rules to generate concise comments, categorizing issues into bug, risk, nit, or question levels for clear prioritization.

How does automated code review handle severity levels for repository diffs?

Automated code review handles severity levels by applying predefined severity rules to parsed code diffs, categorizing feedback into distinct levels like bug, risk, nit, and question for prioritization.

Do I need to manually trigger code review on every pull request?

You do not need to manually trigger code review on every pull request, as the system triggers automatically when reviewing pull requests or in response to specific commands.

What is the best way to format code review comments for quick bug reporting?

The best way to format code review comments for quick bug reporting is using a single-line format that explicitly identifies the location, problem, and suggested fix.