skills.rest
echowaves
echowavesOFFICIAL
Explore all skills by this author →
WebsiteGitHub

caveman-review

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

Updated Feb 12, 2021
Search Tags:#code review#pull requests#developer productivity#actionable feedback#severity labels#diff commenting
One-click install
npx skills add https://github.com/echowaves/WiSaw.cdk --skill caveman-review-echowaves
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/echowaves/WiSaw.cdk/tree/main/.agents/skills/caveman-review
Command: npx skills add https://github.com/echowaves/WiSaw.cdk --skill caveman-review-echowaves

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill cuts down noisy, verbose pull request feedback into ultra-compressed, actionable comments that are easy to scan and act on during code review.

Core Features & Use Cases

  • One-line, high-signal findings: Produces a single comment per finding with a strict format of location, problem, and fix.
  • PR-review optimized output: Auto-triggers for PR review requests and supports multi-file diffs using a file-and-line location format.
  • Severity-aware guidance: Adds optional severity prefixes (🔴 bug, 🟡 risk, 🔵 nit, ❓ q) so reviewers can prioritize issues.

Quick Start

Ask for: Review this PR using caveman-review format with one line per finding as Location, problem, fix.

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

Concise code review comments require a strict format of location, problem, and fix on a single line. This approach preserves actionable signal while removing noise, making PR feedback easy to scan and act on during reviews.

What is the best way to add severity labels to PR diff comments?▼

Severity labels like bug, risk, nit, and question can be added as prefixes to PR diff comments. This severity-aware guidance helps reviewers prioritize issues quickly within one-line, high-signal findings.

Can I generate one-line actionable feedback for JavaScript and TypeScript codebases?▼

Yes, you can generate one-line actionable feedback for JavaScript and TypeScript codebases. The review format applies to PR diffs in these environments to provide fast, scannable feedback with exact locations.

How do I format multi-file PR diffs for fast scannable review feedback?▼

Multi-file PR diffs are formatted using a file-and-line location structure. Each finding produces a single comment containing the exact location, the problem, and the concrete fix for fast scanning across the diff.

Does ultra-compressed PR review format work for noisy pull request feedback?▼

Yes, the ultra-compressed PR review format is designed specifically to cut down noisy, verbose pull request feedback. It drops unnecessary information and keeps only terse, actionable signal for review quality.

Related Skills

Explore More Software Engineering Skills→
huangzidahuangzida
2

caveman-review

Generate terse one-line code review comments for pull request diffs.

Community
Intermediate
hyperlane-xyzhyperlane-xyz
97

inline-pr-comments

Post line-specific inline comments to GitHub pull request diffs.

Official
Intermediate
BaiGanioBaiGanio
7

preprocess-pdf

Interprets PDF preprocessing results to guide routing decisions.

Community
Intermediate
achmfachmf

caveman-review

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

Community
Basic