skills.rest
SimonZimmer
SimonZimmerCOMMUNITY
Explore all skills by this author →
GitHub

caveman-review

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

Updated Jun 16, 2022
Search Tags:#code review#feedback#pull request#github#diff#severity#review comments
One-click install
npx skills add https://github.com/SimonZimmer/dotfiles --skill caveman-review-simonzimmer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/SimonZimmer/dotfiles/tree/main/.config/opencode/skills/caveman-review
Command: npx skills add https://github.com/SimonZimmer/dotfiles --skill caveman-review-simonzimmer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review feedback is often buried in verbose, hedged prose that obscures the actionable point. This Skill compresses PR review comments into single lines containing the exact location, severity, problem, and concrete fix, so authors can act on feedback immediately. ## Core Features & Use Cases - Terse Comment Format: Outputs each finding as L<line>: <severity> <problem>. <fix>. with severity emoji (🔴 bug, 🟡 risk, 🔵 nit, ❓ question) and backticked symbol names. - Noise Filtering: Drops throat-clearing, hedging, per-comment praise, and restatements of what the diff already shows. - Auto-Clarity Mode: Switches to full explanatory paragraphs for CVE-class security findings, architectural disagreements, and onboarding contexts, then resumes terse output. - Use Case: Paste a pull request diff and ask for a review; receive a ready-to-paste list of line-anchored comments like L42: 🔴 bug: user can be null after .find(). Add guard before .email. ## Quick Start Ask the assistant to review this pull request diff using caveman-review and output one-line comments for each finding.

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 comments for a pull request?▼

Invoke the skill with "/caveman-review" or phrases like "review this PR" or "review the diff". It outputs one line per finding in the format L<line>: severity, problem, fix, ready to paste into the PR.

What format do the code review comments use?▼

Each comment follows `L<line>: <severity> <problem>. <fix>.` with an optional file prefix for multi-file diffs. Severity emoji indicate 🔴 bug, 🟡 risk, 🔵 nit, or ❓ question, and symbol names appear in backticks.

When does caveman-review switch to verbose explanations?▼

It drops terse mode for CVE-class security findings, architectural disagreements, and onboarding contexts where the author needs the reasoning. After that finding, it resumes one-line output for the rest of the review.

Can caveman-review approve PRs or run linters?▼

No. It only outputs review comments and does not approve or request changes, write code fixes, or run linters. Saying "stop caveman-review" or "normal mode" reverts to verbose review style.

Why are my review comments too long or hedged?▼

Default review style includes hedging and restating the diff. This skill strips phrases like "I noticed that" and "you might want to consider", replacing them with a direct problem statement and concrete fix per line.

Related Skills

Explore More Software Engineering Skills→
NeoLabHQNeoLabHQ
1.5k

attach-review-to-pr

Add line-specific review comments to GitHub pull requests via the gh CLI API.

Official
Intermediate
learntocloudlearntocloud
801

review-pr-comments

Triages and addresses pull request review comments using the GitHub CLI.

Official
Intermediate
phraphra

code-review

Review modified code files and auto-fix mechanical issues.

Community
Advanced
ng-namanhng-namanh

junior-mentor

Generate structured code change explanations covering scope, rationale, alternatives, and tips.

Community
Advanced