skills.rest
rvdbreemen
rvdbreemenCOMMUNITY
Explore all skills by this author ā†’
GitHub

caveman-review

Generate one-line code review comments with line numbers and fixes.

199|41|Updated Oct 25, 2020
Search Tags:#diff analysis#code review#pull request#actionable fixes#one-line comments#severity labels
One-click install
npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill caveman-review-rvdbreemen
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/rvdbreemen/OTGW-firmware/tree/main/.agents/skills/caveman-review
Command: npx skills add https://github.com/rvdbreemen/OTGW-firmware --skill caveman-review-rvdbreemen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

caveman-review removes noisy, verbose code review commentary and replaces it with compact, paste-ready findings that include the exact line reference plus a concrete fix.

Core Features & Use Cases

  • Ultra-compressed one-line findings: produces output in an L<line>: <severity> <problem>. <fix>. format for quick triage.
  • Consistent severity labeling: uses šŸ”“ bug, šŸŸ” risk, šŸ”µ nit, and ā“ question to distinguish urgency from style and uncertainty.
  • Noise reduction rules: avoids throat-clearing, hedging, and restating what the diff already shows, while keeping actionable details and backticked symbol names.

Quick Start

Ask the assistant to review the diff and generate one-line PR comments in the requested L<line> format.

Frequently Asked Questions about caveman-review

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

FAQPage Schema
How do I generate actionable code review comments for a pull request diff?ā–¼

To generate actionable code review comments for a pull request diff, convert diff findings into one-line statements that include the exact line reference and a concrete fix. This produces ultra-compressed, paste-ready findings for quick triage.

What is the best way to format pull request feedback to reduce noise?ā–¼

Formatting pull request feedback to reduce noise involves using an ultra-compressed one-line output format like `L<line>: <severity> <problem>. <fix>.`. This removes throat-clearing and hedging while keeping actionable details and backticked symbol names.

Can I use severity labels to distinguish urgency in code review comments?ā–¼

Yes, you can use severity labels to distinguish urgency in code review comments by applying consistent prefixes such as šŸ”“ bug, šŸŸ” risk, šŸ”µ nit, and ā“ question. This clearly separates critical bugs from style nits and uncertainty.

Does this code review approach work for multi-file diffs?ā–¼

Yes, this code review approach works for multi-file diffs. It applies when reviewing code changes across single- or multiple-file diffs, preserving line numbers and boundary rules to output review comments only.

Why do my PR review comments restate what the diff already shows?ā–¼

PR review comments restate what the diff already shows due to verbose commentary and lack of noise reduction rules. Applying strict output format requirements and boundary rules eliminates restating the diff and keeps only actionable fixes.

Related Skills

Explore More Software Engineering Skillsā†’
fmflurryfmflurry
171

caveman-review

Generate terse one-line code review findings from pull request diffs.

Community
Intermediate
hyperlane-xyzhyperlane-xyz
97

inline-pr-comments

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

Official
Intermediate
CapplequoppeCapplequoppe

review-github-pr

Automate GitHub pull request reviews by fetching diffs and posting comments via GitHub CLI.

Community
Intermediate
austinwilcoxaustinwilcox
1

caveman-review

Generate one-line code review comments with locations and fixes for PR diffs.

Community
Basic