skills.rest
kaitoartz
kaitoartzCOMMUNITY
Explore all skills by this author →
Website𝕏@kaitoartzzGitHub

caveman-review

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

Updated Jun 30, 2026
Search Tags:#code review#pull request#github#PR feedback#diff#review comments#terse feedback
One-click install
npx skills add https://github.com/kaitoartz/dotfiles --skill caveman-review-kaitoartz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-review
Source: https://github.com/kaitoartz/dotfiles/tree/main/dot_gemini/config/skills/caveman-review
Command: npx skills add https://github.com/kaitoartz/dotfiles --skill caveman-review-kaitoartz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request feedback is often buried under hedging, filler phrases, and restated code, making reviews slow to write and tedious to read. This Skill compresses every review finding into a single actionable line so reviewers communicate signal without noise. ## Core Features & Use Cases - One-line findings: Each comment follows the format L<line>: <problem>. <fix>. with exact line numbers and symbol names in backticks. - Severity prefixes: Optional emoji tags distinguish bugs (🔴), risks (🟡), nits (🔵), and genuine questions (❓) when severity is mixed. - Auto-clarity fallback: Security findings, architectural disagreements, and onboarding contexts automatically expand into full explanatory paragraphs. - Use Case: A reviewer pastes a multi-file diff and receives paste-ready comments like auth.py:L42: 🔴 bug: user can be null after .find(). Add guard before .email. ## Quick Start Review this pull request diff and give me caveman-style 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 write shorter code review comments?▼

Use the format L<line>: <problem>. <fix>. with exact line numbers and symbol names in backticks. Drop hedging phrases like "you might want to consider" and restating what the code does; state only the problem and concrete fix.

How to review a pull request diff quickly?▼

Invoke the review with a phrase like "review this PR" or "/review" and paste the diff. The output is one paste-ready comment per finding, prefixed with file and line number for multi-file diffs.

What do the severity prefixes in review comments mean?▼

🔴 bug marks broken behavior that will cause an incident, 🟡 risk marks fragile code like races or missing null checks, 🔵 nit marks ignorable style issues, and ❓ q marks genuine questions rather than suggestions.

When should code review comments not be terse?▼

Terse mode is dropped for security findings needing CVE-class explanation, architectural disagreements requiring rationale, and onboarding contexts where a new author needs the reasoning. Normal paragraphs are written for those, then terse style resumes.

Can caveman-review write the code fixes or approve PRs?▼

No. It only outputs review comments ready to paste into the PR. It does not write code fixes, approve or request changes, or run linters; saying "stop caveman-review" reverts to verbose review style.

Related Skills

Explore More Software Engineering Skills→
segersnielssegersniels

Review PR

Analyze pull request diffs to generate prioritized feedback on bugs, style, and security.

Community
Intermediate
OmniloyOmniloy

review-pr

Resolve GitHub pull request review comments with fixes and re-review requests.

Official
Advanced
eliottbusinesseliottbusiness

requesting-code-review

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

Community
Advanced
xiaoshuangLixiaoshuangLi
1

code-review

Review code against a six-dimension checklist for correctness, security, and maintainability.

Community
Intermediate